The order to do it in
Dependencies run downhill, so import in this order:1
Upload assets
Optional. Upload brand assets such as logos first; the returned asset IDs are referenced by chain records.2
Import chains
A store cannot be imported before its chain exists.3
Import stores
4
Import opening hours adjustments
5
Read back
Use the retrieval endpoints — search and get-by-id — from your internal services.Chains
Chains represent the retailer’s brands. A retailer may have several, each with its own identity.
Chains can be read individually or in full, which is what internal services use for validation and lookups.
Stores
Stores can be fetched by ID, searched free-text, or paged through when the estate is large. They can be imported directly or through the Data Import Service. Once imported, the data is immediately available to every other service that consumes Store Service.
Updates use the same endpoints as creation — address corrections, contact details, revised coordinates, status changes and new alternate IDs all arrive as upserts.
Removing a store
There are two ways, and they behave differently:- Set its
statustoClosed— the store stays in the system but is hidden from operational features. - Omit it from a full import — see the import modes below.
Opening hours
Regular opening hours are the store’s default weekly schedule — Monday 08:00–22:00, Sunday closed, and so on. Adjustments override that schedule for a date range, and exist for public holidays, special events, seasonal changes, renovations and unexpected closures. An early close on Christmas Eve, a week-long shutdown, or extended hours during a promotion are all adjustments.Import modes
Incremental is the safer default. Reach for full only when the source really is the authoritative master for the whole estate.