Skip to main content
Where to find it: Settings → Management → Products — Open in OTO ↗
The product record is the single most leveraged piece of data in the platform. A barcode typed in once decides whether a picker can scan a box three years later; a weight left blank turns up as an unexpected carrier charge every month until someone fills it in.

​
Where the catalog lives

Settings → Management → Products, with four tabs: Three buttons sit above it: Add Product, Upload Multiple Products for a bulk import from a template, and Synchronize Products to pull the catalog from your connected sales channels.
The Products page

Fig. 1 — Every row carries a thumbnail, and Pre order Only and Variants Enabled read as Yes/No chips rather than raw values.

​
The product record

The top of the Add Product form

Fig. 2 — Only Product Name, SKU and Price are required. The tab row grows as options are switched on — here Product Variants and Variant Configurations have appeared.

​
Identity

​
Commercial

Price and Tax Amount each carry their own currency selector, so a catalog can hold products priced in different currencies rather than forcing one and converting. Pre order Only marks a product that may be ordered before stock exists; orders containing one are held rather than released — see Pre-fulfillment checks.

​
Weight and dimensions

Length, Width and Height in centimetres, Total Weight in kilograms, and Cubic Meter in cm³ — each with a stepper, and each unit shown in the field so nobody has to guess.
The rest of the product form

Fig. 3 — Dimensions, the bundle and serial switches, tags, the two kinds of barcode, and the packaging-barcode table once it is enabled.

This is the field people skip and then pay forCarriers charge on whichever is greater, actual or volumetric weight, and they reweigh at their own depot. A catalog with missing dimensions produces shipments quoted at one price and invoiced at another, and the difference only surfaces in invoice reconciliation weeks later. Filling these in once is the cheapest shipping saving available.

​
Multiple barcodes per SKU

One product can carry several barcodes, and there are two distinct reasons to want that.

​
Other Barcodes

Several codes that all mean one unit of this product: a manufacturer’s EAN, a warehouse-applied label, an old code from a previous supplier, a marketplace’s own identifier. All of them scan to the same product, so nothing has to be relabelled and no picker has to know which generation of sticker is on the box.

​
Packaging Barcodes

A different idea, turned on with Enable Packaging Barcodes. The product’s own description: “Allow products to have packaging-specific barcodes with custom quantities per scan (e.g., boxes, cases, pallets).” Switching it on opens a table with three columns, one row per packaging level:
The packaging-barcode table with the UOM list open

Fig. 4 — Four levels, so a product can carry a barcode for the unit, the box, the case and the pallet at once.

One scan, twenty-four unitsA case of twenty-four has its own barcode and its own row, with Units per Scan set to 24. Without this, receiving a pallet means opening cases and scanning singles, or trusting a typed number. With it, the case barcode is twenty-four — the scan carries the quantity.The saving compounds at every touch: goods-in, putaway, counting and transfers all stop being per-unit work on products that arrive by the case. And because all four levels can coexist on one product, the same item can be received by the pallet and picked by the unit without anyone changing a setting.

​
Bundles and kits

Turn on Bundle Product and the product becomes a container. A table opens beneath it, one row per component:
A bundle and its components

Fig. 8 — Two columns and nothing more: which SKU goes in, and how many of it. Each row is confirmed with a tick before it counts.

The bundle is sold as one line and handled as its parts. The order shows a gift set; the warehouse picks and packs the items inside it separately, each against its own stock. So a component running out makes the bundle unsellable automatically, without anyone maintaining a second stock figure for the bundle itself.
Quantity is what makes this more than a groupingA bundle containing two of one component and one of another is not a list of three products — it is a recipe. Getting the quantity into the definition means the picker is told to fetch two, the availability calculation knows that a bundle needs two, and a stock of five of that component supports two bundles rather than five.It is the difference between a bundle that stays sellable because nobody did the arithmetic, and one that goes out of stock at the right moment.

​
Serial number tracking

Two fields govern it: Serial Number Requirement and Serial Number Type. Requirement is what decides whether an operator is stopped, prompted, or never asked.
The Serial Number Requirement options

Fig. 5 — Three states, and the middle one matters: Not Applicable is an explicit answer, not an empty field.

Validation runs at both picking and packing. On the pick screen, once an item is picked — scanned or entered by hand — a Serial Number button appears for products whose requirement is set to required or optional. The operator enters or scans the serial, and it is validated immediately: if it does not validate, picking cannot be completed for that order until the correct serial is supplied.
Catching it at the pick, not the packValidating only at packing means a wrong unit has already been walked to the bench before anyone notices, and the picker who fetched it has moved on. Validating at the pick means the correction happens at the shelf, where the right unit is within arm’s reach.It is the same check in both places, so the cost of adding the earlier one is a second per serialized item — against a returns case that costs considerably more than that.
Serial numbers matter wherever a warranty, a recall or a dispute attaches to a specific unit rather than to a SKU: electronics, appliances, anything with a registration.

​
Variants

Product Variants, in the product’s own words, lets you “add different options like size or color.” Switching it on adds two tabs to the form — Product Variants and Variant Configurations — and the catalog list carries a Variants Enabled column so you can see at a glance which products are structured this way.
The Product Variants tab

Fig. 6 — A variant is a name and a list of options. Add Another Variant stacks a second dimension on the first.

Naming in both languages, at the point of creationA storefront serving Arabic and English readers needs both names for every variant dimension. Capturing them together, on the form that creates the variant, is what stops the second language becoming a migration project later — and it is why the field sits beside the first rather than in a translation screen.

​
Handling that depends on the goods

Some categories carry requirements that change what the warehouse is allowed to do with a unit rather than just describing it. Not all of them live on the product record — an expiry date, for instance, is captured on the receipt that brings the stock in.

​
Per-channel settings on the product

The form’s Sales Channel Sync tab is a table, one row per channel this product is listed on.
The Sales Channel Sync tab

Fig. 7 — Each row ties this product to its identity on one channel — and can override how stock is calculated for it.

Two levels of the same controlInventory Calculate Method and Inventory Sync both appear here and on the channel’s own sync settings. The channel setting is the default; the product row is the exception.That is what lets a single line be protected with safety stock on a marketplace that penalizes cancellations, while the rest of the catalog on that same channel sells down to the last unit — or lets one problem SKU be taken out of sync without touching anything else.

​
Custom attributes

When the standard fields do not cover what your business needs to record, Product Attributes adds your own: a name and label, a type, an optional default value, and a flag for whether the attribute appears in imports. Attributes can be gathered into Attribute Groups, and each group becomes its own tab on the product form — so a form stays readable however many fields a category needs.

​
Getting the catalog in

Bulk uploads are tracked at Settings → Data Center → Data Uploads, which reports what imported and what did not, with the errors named per row. Worth opening after every import rather than assuming a file that uploaded also landed.