Product model

Every catalog connector, whatever the system behind it, returns products in one normalized shape. Matching, quantity math, dietary filtering, and cart assembly all read that shape rather than your raw payload, so the work of integration is a mapping exercise rather than a rewrite.

Fields

• sku — your identifier for the product, as a string. Neomi keys everything on it and passes it back when the cart is handed over.

• name — the display name a shopper sees.

• price — the base price as a number.

• special_price — the promotional price, when one applies.

• image — a resolvable image URL.

• brand — brand name, where you hold one.

• weight — the size or pack descriptor, such as a net weight or volume.

• stock — an availability object. See the stock model.

• categories — the category path the product belongs to.

• attributes — the open bag where dietary and other structured attributes live.

Quantity fields

Two fields govern how much of something a shopper can buy: a recommended quantity step, and a minimum salable quantity. Both matter for weighed goods, where a step of 0.1 kg and a minimum of 0.3 kg produce a very different cart than a step of one unit.

Required fields

A product without an identifier or a name is dropped rather than passed through, because it cannot be keyed or added to a basket. Everything else is optional and degrades gracefully: a missing image weakens the interface, a missing brand does not.

Note on this page

Described from the current implementation rather than from a published contract. Field names and shapes are what Neomi normalizes to today; our engineering team confirms the public naming when the reference is finalized.