POS items and catalog

Bitta Retail POS keeps its own lightweight catalog - POS Items, POS Customers, and Categories - that works standalone out of the box and can optionally be mapped to standard Business Central Items and Customers for end-of-day posting. This page covers the catalog records and the mapping workflow; how items display on the register is covered in Register layout and assortment.

POS Items

The POS Item is the register-facing catalog record. Open Tell Me (Alt+Q) and search POS Items; each row opens the POS Item Card. Key fields:

Field	Default	What it does
POS Item No.	next number from the POS Item Nos. series	Primary key, auto-assigned when left blank.
Description / Short Description	-	Full name plus a 30-character short form for compact register display.
POS Category Code	-	Groups the item under a category tab on the register.
Barcode	-	The item's legacy scan code. It remains a compatibility fallback after standard BC Item Reference resolution - see Barcode setup.
Active	true	Inactive items refuse to sell.
Unit Price / Cost	0	Shelf-price and cost fallbacks for an unmapped POS-only item. A mapped item takes its price from the standard BC price engine for the current customer, location, variant, UOM, quantity, and date.
POS Discount %	0	An item-level promotion candidate that competes with BC line-discount and loyalty candidates as a best offer - it is not stacked on top.
Allow Price Override	false	Per-item gate for manual price changes, combined with the POS Setup master switch and the user's Can Override Price flag.
Tax Group Code	blank	US Sales Tax classification; falls back to the mapped BC item's Tax Group Code when blank.
Show on Register / Register Sort Order / Favorite	true / 0 / false	Register display controls - see Register layout and assortment.
POS Min. Qty. / POS Max. Qty.	0	Per-transaction quantity bounds enforced on every register add path. Zero disables that bound.
Sold by Weight / Scale UOM / Default Tare	off	Weighed-item capture - see the Scale and weighed items lab.
Mapping Status, BC Item No., snapshots	Unmapped	The optional BC link - see below.
Has Variants / Default Variant Code	calculated / blank	Variant policy for mapped items - see Item variants.

An item that has ever been sold cannot be deleted - deactivate it instead. Tile color comes from the item's category and tile size from POS Setup or the terminal; there is no per-item color or size.

Categories

Categories are optional metadata for the item's POS Category Code: a display name, a tab order, a tile color from a fixed palette, and a Show on Register flag that hides the whole tab. They also carry default kitchen-label policy that items inherit - see Kitchen output. A category code used on items but missing from the table still works; the register shows the raw code with default-gray tiles. Find them via Tell Me -> POS Categories.

Mapping POS Items to BC Items

A POS Item can carry a BC Item No.. Mapped items are what end-of-day posting turns into Sales Invoice lines, and the mapping also unlocks variants and the register's stock badges. Every POS Item has a Mapping Status: Unmapped, Mapped, Invalid Mapping (the linked BC item vanished or is blocked), or Auto Suggested (proposed by auto-map, not yet confirmed).

1. On the POS Item Card, choose Map to BC Item and pick from the Item List (blocked and sales-blocked items are filtered out), or type the BC Item No. directly.
2. On success the BC Description, BC Unit Price, and BC Unit of Measure snapshots are copied read-only and the status becomes Mapped. Clearing the field returns the item to Unmapped.
3. Use Remove Mapping to detach; the item keeps selling standalone.

Every modify re-validates the link: a missing, blocked, or sales-blocked BC item flips the status to Invalid Mapping. End-of-day posting errors per sale group when an item is unmapped or its BC item is unusable - one bad item is reported without corrupting other groups. See Consolidated posting.

POS Customers and mapping

POS Customers follow the same pattern: a standalone record with POS-specific fields (discount, credit limit, loyalty card number, notes) that can optionally map to a standard BC Customer via Map to BC Customer. Customers who pay on account or get invoiced at end of day must be mapped; anonymous cash trade stays on the walk-in cash customer, which Assisted Setup creates and maps for you. The same Mapping Status enum and integrity re-checks apply. Day-to-day customer handling at the register is covered in Customers and loyalty at the register, and on-account credit checks in On-account sales.

Auto-Map to Business Central

The Auto-Map to Business Central action - available on the POS Items list, the POS Customers list, and the POS Setup card - scans all unmapped POS Items and POS Customers in one batch and links them to matching BC records:

Entity	Match order
POS Item	1. Barcode against standard Item Reference rows of type Bar Code; 2. exact Description match.
POS Customer	1. exact Name; 2. Phone No.; 3. Email.

Matches are marked Auto Suggested so a human reviews them before they count as confirmed; existing mappings are never changed. Filter the lists on Mapping Status = Auto Suggested, review each row, and confirm by re-validating the BC number - or clear it.

Seeing mappings from the BC side

Bitta Retail POS extends the standard lists: the BC Item List gains POS Item Count and Has POS Items columns, and the BC Customer List gains POS Customer Count and Has POS Customers, so you can see at a glance which BC masters are sold or served at the till. Several POS Items may map to the same BC Item - the counter counts them.