One catalog.
Many ways to sell.
Connect products, customers, and orders to the channels your business needs. Keep commerce data together and design the storefront around your audience.
The everyday vessel
A simple object. A considered detail.
The product, the customer,
and everything after the order.
Commerce work continues beyond a storefront. Connect the catalog, customer context, business decisions, and operational trail in the same foundation.
Give every product
the detail it deserves.
Keep names, variants, product media, and language-specific descriptions together. Add typed custom fields for the attributes your business needs instead of hiding important information in a generic description.
- Structure variants and product information
- Extend the catalog with business-specific attributes
- Connect media and localized descriptions
The everyday vessel
Example product · VES-001An order belongs
to a customer relationship.
Connect orders and subscriptions to the selected customer context. The same person can belong to more than one business, so make the active customer clear before showing or changing their commerce records.
- Show records for the selected customer
- Connect people through customer memberships
- Keep the business context visible in your portal
Northstar Studio
Customer contextRecords are presented for the selected customer.
Atlas Collective
Customer contextRecords are presented for the selected customer.
Express the decision
behind the next step.
Use rules to describe which records qualify, then connect events to the actions you configure. A first-order follow-up and a returning-customer path can be different branches of the same automation.
- Build around an explicit business event
- Keep the qualifying criteria understandable
- Follow the branch that matched the record
Follow the event, decisions, and actions.
A product story
for each market.
Prepare product information in multiple languages while keeping one catalog record. Default-language values stay available until a translated field is enabled; bulk auto translation helps prepare a selected product set.
- Translate collections as a content set
- Enable local wording where it is needed
- Review generated values before they go live
Default language (English)
Everyday essentials, made with care.
Bulk auto translation prepares selected records in one or more target languages.
Know what happened
after the request.
Inspect the execution behind a business action: who acted, which decisions applied, and what changed. External delivery belongs to a related outbox, so internal completion and external delivery do not get confused.
- Follow actions and rejection reasons
- Connect record changes to their execution
- Inspect the delivery attempts for external work
execution / example-042- 01RequestUpdate a product
Actor and customer context
- 02DecisionAllowed to proceed
Permissions and rules evaluated
- 03ChangeProduct updated
Recorded outcome
- 04OutboxExternal work queued
Delivery has a separate state
Inspect the action through its outcome.
Explore the details.
The capabilities, examples, and integration choices behind this solution.
Connect the operation.
Shape the experience.
Choose the commerce capabilities around your catalog, customers, and the channels you want to serve.