Product data rules
Which product fields you own and which we own, and what happens when a field changes after modelling has started.
You own the product information; we own the 3D work. These rules apply to every call that sends product data.
Who owns which field
| You own (we update from your calls) | We own (your calls never change these) |
|---|---|
| Name, category, subcategory, product link | Production status |
| Dimensions and 3D source file (see the rule below) | The 3D model, AR files and delivery |
| Reference images (added, never removed) | Images and renders we produce |
| Variants (added, never removed) | Viewer and AR links |
Discontinued (active) | Pricing |
- An empty field never clears ours. If you leave out
category, we keep the one we have. - Reference images are only ever added. We skip images we already have, up to 10 per product.
- Variants are only ever added. A variant with its own
articleIdbecomes its own product with us.
The dimension rule
- Before modelling starts, a change to
dimensionsCmorsource3dUrlapplies straight away. - After modelling has started, the same change could make the model wrong, so we never apply it silently. The answer is
change_requestwithpendingChanges(field,from,to,requestedAt), and our production team picks it up with you. - Name, category and product link keep updating at any stage.
Discontinued products
- Send
"active": falseto tell us a product is discontinued in your system. We record it; nothing already made is removed. - Send
"active": trueto bring it back.
Article numbers are yours
- An article number is unique within your account: one number is one product, and sending a number we already hold updates that product.
- Another company may use the same number for its own product; that never touches yours, and we never look at it.