Zopping
Get a token

Multi-store & marketplace

A Zopping organization can run many stores, and a marketplace org can host many sellers. This guide covers operating across both — the advanced companion to the catalog and order basics.

Stores

Catalog is org-wide, but price, stock and fulfilment are per store. Most operational reads and writes take a storeId:

# Price/stock for one store
curl "https://zopping.com/api/inventory-service/item?organizationId=<org-id>&storeId=<store-id>&productId=88120" \
  -H "Authorization: Bearer $ZOPPING_TOKEN"

# List the org's stores
curl "https://zopping.com/api/account-service/store?organizationId=<org-id>" \
  -H "Authorization: Bearer $ZOPPING_TOKEN"

Patterns:

  • A product exists once; items exist per store. Create the product org-wide, then upsert an item per store you sell it in.
  • Orders, slots, delivery areas and stock overrides are all store-scoped — always pass the storeId you're operating on.
  • Map your own store ids with clientStoreId on items.

Marketplace (sellers)

On a marketplace org, catalog and inventory can be seller-scoped. Where supported, pass sellerID to act within one seller's catalog:

curl "https://zopping.com/api/catalogue-service/product?organizationId=<org-id>&sellerID=55" \
  -H "Authorization: Bearer $ZOPPING_TOKEN"

Sellers can also request products into the shared catalog (catalogue-service/seller-product-request), which the org approves.

Good practices

  • Never assume a single store — read the store list and operate per storeId.
  • Scope every operational write (price, stock, orders, slots) to its store.
  • Use clientStoreId / clientId to keep a stable mapping to your own store and product ids.

Reference: Inventory · Orders · Stores in Catalog.