Products

Products give SKUU one complete, authoritative view of the sellable catalogue.
SKUU reads this view from the customer API and uses it for product matching,
availability and later order flows.

What the catalogue represents

A catalogue contains two levels:

• a product holds shared information such as title, brand, description,
  category, tags and images;
• a variant is one sellable choice with its own stable identifier,
  attributes, price and stock per location.

Each scheduled traversal is a complete snapshot. Only a fully traversed and
validated snapshot becomes authoritative.

Product images

Include product image URLs whenever they are available. Place the primary image
first, followed by alternate views. SKUU stores the first URL as the primary
image and retains up to three additional URLs.

Images belong to the product and apply to its variants. SKUU stores the URLs;
it does not download or cache the image files. A product with no image may send
an empty list or omit the field.

How variants are identified

Each variant keeps the platform's stable variant_id. For matching, provide
the strongest route already present in your catalogue:

1. an exact barcode;
2. an exact customer SKU; or
3. product title together with structured size and colour.

A barcode is useful but not mandatory. Do not invent placeholder values or
reimplement SKUU's matching score.

Availability controls

Two optional product tags control participation in the network:

• SKUU_Exclude stops the product's physical stock from contributing to peer
  availability;
• SKUU_Stop stops peer availability from being added to the corresponding
  product in your catalogue.

Other tags remain catalogue metadata and do not change SKUU behaviour unless
separately agreed.

Stock baseline

Every variant includes an absolute quantity for each agreed physical location
and for the virtual SKUU_Network location. Zero quantities are included
explicitly. The customer owns physical quantities; SKUU owns the virtual
network quantity.

Pagination

Large catalogues are returned in pages. The first request has no cursor. When
another page exists, the response supplies an opaque cursor that SKUU uses in
the next request. A null or omitted cursor ends the snapshot.

Technical reference

See Read products
for the exact endpoint, fields, image schema, pagination rules, authentication
and response examples.