Products and SKUs
Learn more about the standards related to products and SKUs
Last updated
Learn more about the standards related to products and SKUs
Last updated
The checklist items and standards in this section cover how to manage your products in the Digital River APIs.
On this page, the integration checklist that you should use depends on the product data model you employ. For more information, refer to the:
section on the Describing line items page
The integration checklist you should work from in this section depends on your product data model.
Click any checklist item for more details on meeting the integration standard.
The product and SKU standards that apply to your integration depend on which of the above ☝️ checklists you're using.
Product catalogs are often very large. To optimize performance, you should synch your products and SKUs on a timed schedule or using a similar trigger.
When you set these values in your admin interface, you can sync your products with their corresponding SKUs in Digital River's system.
You should have a tool that manually imports and then allows you to periodically update your products in Digital River's system through the . Your platform's admin interface most likely already has a product management page. You can simply modify this page to perform .
These scheduled jobs should make as few calls to the as possible. Therefore, we suggest you use a delta to only update the attributes in a SKU that changed in its corresponding product. This prevents you from having to overwrite every SKU value each time you run a synchronization job.
If you're by referencing SKUs that don't belong to SKU groups, then you should add the following attributes to the product schema in your commerce platform:
Similarly, regardless of whether or not you associate SKU groups with SKUs, if you're by referencing SKUs, you should also add the following attributes to your platform's product schema:
Your product's identifier should match the in our system. It's important that these values are the same. This ensures that synchronization is possible and that the SKUs work properly during checkouts.
Before deployment, you should .
Before deployment, you should .
, ,