CreateStandardProductInput
Input parameter for the createStandardProduct
mutation. A standard product ref
should be unique within the bounds of the specified catalogue
, which together makes up the unique identifier for the StandardProduct
record.
The following default values will be set on creation:
-
status
=CREATED
-
workflowRef
=PRODUCT_CATALOGUE::<product_catalogue.type>
-
workflowVersion
=<Workflow.majorVersion>.<Workflow.minorVersion>
.
After data persistence, an orchestration event will be fired providing the opportunity to perform business logic within a workflow.
Backward Compatibility Note
With the introduction of Global Inventory, we have introduced new data structures to support this functionality. Existing orchestration enabled clients will have access to their existing product based data via theCOMPATIBILITY:<retailerId>
catalogue.
For more information, please refer to the Backward Compatibility Guide on Lingo
Input Fields
String!
)
The unique reference identifier for the Product.
Max character limit: 100.
ProductCatalogueKey!
)
The Product Catalogue in which this Product is managed
String!
)
Type of the StandardProduct
, typically used by the Orchestration Engine to determine the workflow that should be applied. Unless stated otherwise, no values are enforced by the platform.
Max character limit: 50.
[AttributeInput]
)
A list of attributes associated with this Product. This can be used to extend the existing data structure with additional data for use in orchestration rules, etc.
String!
)
The Global Trade Item Number (GTIN) for this Product.
Max character limit: 20.
String!
)
The name of the Product
String
)
A short description of the Product (max 255 chars)
[CategoryKey]
)
A list of references to the Category
's to which this Product
relates. Product categories must be a part of the same ProductCatalogue
(see catalogue
field). The Category
must already exist.
[PriceInput]
)
A list of Prices for this Product
TaxTypeInput
)
The tax information for this Product
[VariantProductKey]
)
A list of references to the VariantProduct
's to which this Product
relates. Product variants must be a part of the same ProductCatalogue
(see catalogue
field). The VariantProduct
must already exist.