> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duitpos.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Products
> Add and manage the items sold at your POS and online.
**Products** are the items customers can order at your POS and online. Each product belongs to a category, can have modifiers and tax rates, and supports **context-specific overrides** — meaning you can set different prices, names, or availability for specific locations and order modes without changing the base product data. For example, a burger costs $12 normally, but $14 for delivery orders, or \$10.99 at your downtown location. This keeps your base menu clean while giving you fine-grained control where you need it.
## Product Fields
| Field | Required | Description |
| -------------- | -------- | -------------------------------------------------------------------------------------------------------------------- |
| **Name** | Yes | The product name displayed on the POS, receipts, and online menu |
| **Code / SKU** | No | An optional internal reference code for stock management or reporting |
| **Price** | Yes | The base selling price (applies everywhere unless overridden). Excluding tax unless tax-inclusive pricing is enabled |
| **Category** | Yes | Which category this product belongs to. Determines where it appears on the POS |
| **Tax** | No | The tax rate to apply per sale. See [Tax](/features/tax) |
| **Brand** | No | Optional grouping under a named brand. See [Brands](/features/brands) |
| **Barcode** | No | One or more barcodes that can be scanned to add the product to a ticket |
| **Image** | No | A photo shown on the online ordering page |
| **Active** | No | Toggle off to hide the product from the POS and online menu without deleting it |
Set your base **Price** as the standard selling price. If you need a different price for delivery, a specific location, or another context, use the **Pricing & Availability** tab (below) to create an override — this keeps the base price clean for in-store use.
## Create a Product
Select a category in the Menu Builder first to scope where the product appears. Or navigate via the Products sidebar link.
Fill in the required fields: Name, Price, and Category.
In the **Modifiers** tab, attach modifier groups (e.g. Size, Add-ons). See [Modifiers](/features/modifiers).
Click **Create** (or **Save** on the edit page). The product is immediately available on the POS.
## Edit a Product
Click the **Edit** icon on any product row to open the product editor. The editor has four tabs — plus two more, **Stock** and **Linked Entries**, if your account has the **Retail & Inventory** module enabled:
* **Details** — Product name, price, category, tax, brand, barcode, image, and active status.
* **Variants** — Link variant products (e.g. different sizes) if you've organized them as separate products.
* **Modifiers** — Attach modifier groups (e.g. Size, Add-ons) and select which modifiers apply to this product.
* **Pricing & Availability** — Set context-specific price, name, and availability overrides per location and/or order mode (see below).
* **Stock** *(Retail only)* — Inventory tracking settings for this product. See below.
* **Linked Entries** *(Retail only)* — Every purchase/sales document that references this product. See below.
All fields are editable. Price changes take effect on the next order placed after saving.
## Pricing & Availability Overrides
The **Pricing & Availability** tab lets you override a product's base price, display name, and visibility for specific locations and/or order modes. This is useful for delivery surcharges, location-specific pricing, time-based promotions, or hiding products in certain contexts.
### How Overrides Work
An **override** is a row that specifies:
* A **Location** (or blank for all locations)
* An **Order Mode** (or blank for all order modes)
* An **Override Price** (or blank to use the base price)
* A **Display Name** (or blank to use the base name)
* **Visibility** — Inherit (use base active status), Visible (show in this context), or Hidden (hide in this context)
**The key rule: blank Location/Order Mode fields mean "applies everywhere," not "applies nowhere."** For example:
* An override with Location = *Downtown* and Order Mode = *blank* applies to all order modes at Downtown.
* An override with Location = *blank* and Order Mode = *Delivery* applies to delivery orders at all locations.
* An override with both blank applies everywhere (this is the global default).
### Override Priority
When an order comes in, the system picks the most specific override that matches. **Each field (price, name, visibility) resolves independently** — meaning a single product's price can come from a location-only override while its name comes from an order-mode-only override.
Priority order (highest to lowest):
1. **Both Location and Order Mode specified** (Priority 1100) — most specific match.
2. **Location only** (Priority 1000) — applies to that location across all order modes.
3. **Order Mode only** (Priority 100) — applies to that order mode across all locations.
4. **Both blank** (Priority 0) — global default, applies everywhere if no more specific override exists.
If you set a row's Price, Display Name, and Visibility all to blank, the system automatically deletes that row when you save — it would have no effect anyway.
### Using the Pricing & Availability Tab
On an existing product, click **Edit**, then click the **Pricing & Availability** tab.
Choose the **Location** (or leave blank for all locations) and **Order Mode** (or leave blank for all order modes).
Fill in the **Override Price** (or leave blank to inherit the base price), **Display Name** (or leave blank), and set **Visibility** (Inherit, Visible, or Hidden).
Click **Save**. The override takes effect immediately for new orders in that context.
You can view and edit all overrides for a product in a table on this tab. Each row shows its calculated Priority (auto-computed, read-only) so you can see the order in which overrides are resolved. Use the **Edit** and **Delete** icons to modify or remove rows.
Overrides are resolved independently per field. For example, you might set a location-specific price override but inherit the base display name and visibility. The system picks the most specific match available for each field separately.
Any override row where all three fields (Price, Display Name, Visibility) are blank gets automatically deleted when you save — it would do nothing anyway.
## Stock tab
Only visible if your account has the **Retail & Inventory** module enabled — see [Retail Overview](/retail/overview).
The Stock tab is where you turn on inventory tracking for this specific product and configure how it's tracked, costed, and reordered. It's the same [Stock Profile](/retail/stock-profile) settings covered in detail on that page — UOM, reorder level, batch/expiry tracking, and the sales/purchase "purpose" flags — surfaced directly on the product so you don't need to jump to a separate screen for the common case of setting up one product at a time.
## Linked Entries tab
Only visible if your account has the **Retail & Inventory** module enabled.
The Linked Entries tab shows every [Purchase Order](/retail/purchase-orders), [Goods Receipt](/retail/goods-receipts), [Purchase Invoice](/retail/purchase-invoices), and [Sales Invoice](/retail/sales-invoices) that references this product, grouped by document type. Click through any entry to open that document directly — useful for answering "when did we last sell this?" or "which supplier invoice included this item?" without leaving the product page.
## Delete a Product
Click **Delete** on the product row.
Products referenced by existing tickets cannot be deleted — the system will block the deletion to preserve historical accuracy. Deactivate the product instead to hide it from the POS while keeping all records intact. You can reactivate it at any time.
## Frequently Asked Questions
Check four things: (1) The product is set to **Active**. (2) The product's **Category** is set to Active. (3) Check the **Pricing & Availability** tab — if the product has a Visibility override set to **Hidden** for the current location/order mode, it won't show even if the base product is Active. (4) Reload the POS app — it caches the menu and may not show changes immediately.
**Hidden** (visibility override) hides the product only in that specific context (location + order mode). The product still appears in other contexts and remains searchable. **Deactivating** the whole product hides it everywhere and takes it out of search. Use Hidden for temporary context-specific removal; use Deactivate if you're retiring a product.
Add one or more barcodes to a product in the **Barcode** field on the Details tab. When staff scan the barcode on a connected scanner, the product is automatically added to the current ticket. You can add multiple barcodes per product (e.g. to cover different packaging sizes of the same item).
The recommended approach is to use **Modifiers** — create a Size modifier group with Small, Medium, and Large options, each with a price adjustment, and attach it to the product. This keeps your product list clean and groups variants together on the POS. Alternatively, you can create separate products for each variant and link them in the **Variants** tab.
Yes. Use the **Import** button on the Products page to upload a CSV file. See [Import History](/reports/import-history) to review the result of any import. If your account has the Retail module enabled, the template automatically includes extra optional columns (UOM, reorder level, batch/expiry tracking, and more) so a product's stock settings can be imported on the same row — see [Importing Retail Data](/retail/importing-data).
## Related
Quickly override prices for multiple products in one context
Organise products into menu sections
Add size, add-on, and customisation options
Assign tax rates to products
Full field reference for the Stock tab
What the Retail module adds to Products