Catalog Objects Provider ID
Catalog Objects Provider ID Usage
To manage catalog object relationships with the POS, we use provider_id
to maintain and share distinct objects across the catalog. Please ensure you do not provide objects multiple times with the same provider_id, we will only ingest one of them leading to unexpected results.
Custom Provider ID
If you need to use a custom provider_id, be mindful of the implications that object duplication can introduce, and only adjust provider_id
when absolutely required.
If your system requires functionality out of the bounds of the provided data models, there may be potential in investigating custom provider_id
adjustments. These adjustments need to be carefully implemented as they can start to cause performance impacts for your customers.
Example with different modifier pricing based on the Item Family
Below we have an example that where we need to have modifiers priced differently, based on the Item Family -> Modifier Group
relationship. In our example, we adjust provider_id
to create a new modifier group for each combination of price, allowing us to continue to share the object when any item family requires the same modifier pricing.
Catalog Object | Provider ID | Price Amount | Modifier Group |
---|---|---|---|
Item Family | burger | drink-100 | |
Modifier Group | drink-100 | ||
Modifier | drink-coke-100 | 100 | |
Modifier | drink-drpepper-100 | 100 | |
Item Family | salad | drink-100 | |
Modifier Group | drink-100 | ||
Modifier | drink-coke-100 | 100 | |
Modifier | drink-drpepper-100 | 100 | |
Item Family | sub | drink-200 | |
Modifier Group | drink-200 | ||
Modifier | drink-coke-200 | 200 | |
Modifier | drink-drpepper-200 | 200 |