Reading product data
For routine syncing, don’t always fetch full data for every product. Base offers lighter-weight methods depending on your need:| I need | Method |
|---|---|
| Basic product list | getInventoryProductsList |
| Full product detail (descriptions, images, variants) | getInventoryProductsData |
| Prices only | getInventoryProductsPrices |
| Stock and reservations only | getInventoryProductsStock |
Bulk updates
Use the bulk methods for writing stock and prices, not one call per product:updateInventoryProductsStock— up to 1000 products/variants per call.updateInventoryProductsPrices— up to 1000 products per call.
Stock reservations
If products come from a native Base inventory (not just a read-only feed), confirming an order automatically reduces/reserves the available quantity — even before your ERP has processed it. This reduces the risk of overselling even if your sync is slower. Current availability and reservations are returned bygetInventoryProductsStock. The connection to orders is covered in Order basic principles.
Product variants
Variants (size, color, etc.) aren’t a separate entity with their own endpoints — they’re part of thegetInventoryProductsData response, and are written/updated with the same bulk methods as main products (updateInventoryProductsStock, updateInventoryProductsPrices), just with variant_id set.
Multiple price groups via a CSV feed
If you need to sync several price groups from feeds at once, a dedicated CSV feed is more efficient than a separate XML file per group:- first column: a clear product identifier (Base ID, SKU, or EAN),
- following columns: individual prices for each price group.
Connecting an external warehouse (your store as a stock source/target) is a different scenario — see Partnership & Shops API.