These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Delivery Slot Management
- Features
- Storefront catalog
Storefront catalog
Storefront catalog records and decisions for a commerce team.
OverviewLive catalogs×
Delivery Slot Management · Storefront catalog
New
Live catalogs
Catalogs
| Catalog code | Name | Currency | Locale | Region | Status | |
|---|---|---|---|---|---|---|
| CC-828 | Catalog 654 | USD | en-US | RGN-622 | Live | |
| CC-637 | Catalog 697 | EUR | en-GB | RGN-292 | Live | |
| CC-786 | Catalog 910 | GBP | fr-FR | RGN-281 | Live | |
| CC-681 | Catalog 671 | CAD | de-DE | RGN-881 | Live | |
| CC-961 | Catalog 424 | AUD | ja-JP | RGN-480 | Live |
6 of 6 records
CC-828Catalogs · CTL-91658
USDNameCatalog 654
Localeen-US
RegionRGN-622
StatusLive
What you can do
Run the work
A catalog gives each market its currency, locale and regional context. A product has its own title, description, publishing state and category; variants carry the sellable SKU, price and shipping requirements. Collections can group products for the storefront. The Catalog Manager keeps these records aligned before a shopper sees them.
How the work is organized
- Define the market. Merchant Owner maintains the catalog currency, locale and live state.
- Prepare sellable items. Catalog Manager maintains product, category, collection and variant details, including SKU and price.
- Check publication. A live catalog and an active product are separate decisions; review both before a shopper sees the range.
Consider a merchant opening another regional storefront. Merchant Owner prepares the new catalog and chooses its currency and locale; Catalog Manager assigns the intended products. A variant’s active flag and price need to agree with the product’s state. The Merchant Owner checks tax and shipping configuration for the region before the catalog is used for orders. This is a practical handoff between merchandising and checkout ownership.
What to agree during setup
Agree stable product handles and SKU conventions, who may change a published price, and how variant changes affect an open basket. Decide which product information comes from the commerce team and which is received from another source. Keep catalog status distinct from a product’s own publication status. A Live catalog can still contain draft products, so review the actual sellable range before opening the storefront.
A pilot should use a real product range, one supported market, a shipping method and a representative order. Confirm which person owns each state change. Review the information that will arrive from payment, carrier and messaging services, and decide how the team will reconcile a delayed or failed response. Keep the customer’s original transaction visible when correcting a later event.
Check the handoff on an actual case
Start with a customer selecting a shippable variant. Compare the item quantity and price in the cart with the resulting booking line. Confirm the delivery address and shipping method. Then follow payment evidence, shipment status and any service request in sequence. If an exception arises, the next person should be able to see the affected booking and the reason for the handoff without guessing from a single overall status.
This exercise also tests access. Catalog Manager should be able to work the records in this module. A colleague with read-only responsibility should be able to inspect the relevant result without gaining permission to change payment or fulfillment evidence. Rehearse an incorrect address and a failed payment result so the team knows how to stop and correct the case.
What your team sees
- Live catalogs — Markets that Merchant Owner has marked Live.
- Open bookings — Orders Catalog Manager can read when a product question arises.
Follow the work through
What it keeps track of
Data model- Catalogs
- A record is a storefront setup for a market, letting the team manage currency, language, and region separately.
- Product categories
- A record is a grouping used to organize products, helping customers and staff browse by type.
- Products
- A record is one item the business sells, used to manage what's listed, its details, and whether it's published.
- Product variants
- A record is one specific version of a product, like a size or color, tracked for pricing and stock.
- Collections
- A record is a curated group of products, used to organize what's shown together on the storefront.
Who uses it
Permissions- Catalog Manager
- Owns the routine handoff.
- Merchant Owner
- Reviews configuration and material exceptions.
- Other configured roles see or update records according to their assigned permissions.
Set up Delivery Slot Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.