Skip to main content
This page covers getting product cards — names, descriptions, images, categories — into the Base catalog. Prices and stock are a separate concern; once your cards are in place, see Prices & Stock for those. Building on the Overview, you have three concrete options.

​
Option 1 — XML feed import

Base can cyclically import product cards from an XML feed in the Heureka or Shoptet specification. If your platform already generates one of these feeds, this is usually the fastest path to get cards into the catalog.
  • Frequency: typically once per day; up to three times per day for enterprise accounts.
  • Downside: in this mode you have no write-side API methods available — the feed content drives everything. You can’t, for example, update a single product field via API while the feed is the source of truth.
  • Custom feed elements: possible on request, but must be configured by the Base team. Contact the implementation team if your feed contains non-standard fields you need Base to read.

​
Option 2 — Fully via API

If you want to control product creation and updates programmatically, use addInventoryProduct.
Sending a product with an existing ID updates that card rather than creating a duplicate. The same method handles both creation and updates — you don’t need a separate “update” call.
Before you create a product, you need its category ID and manufacturer ID. Both are stored on the product as a reference to an existing record, not as free text. If the IDs don’t exist yet, create them first — see Categories & Manufacturers for the relevant methods.

​
Hybrid option — feed for cards, API just for Base IDs

If you create cards via a feed or e-commerce integration but also need the internal Base IDs of newly created products (for example, to hook your own stock sync onto them), use getInventoryProductLogs. This method returns a timestamped log of events for products and their variants in the catalog, including newly assigned IDs. Poll it periodically to detect products the feed has just created and map them to your own internal identifiers.

​
Sync frequency reference

Use this table to set expectations when planning your integration:
If you also need to sync delivery times, or have a specific requirement for the feed structure, contact the implementation team — established approaches already exist for both scenarios.