Commerce at the center.
Your storefront around it.

Build a headless webshop with products, variants, carts, orders, and customer context. Start from the Next.js storefront or bring your own implementation.

Explore the solution
Catalog to storefront
STUDIO / 01

The everyday vessel

A simple object. A considered detail.

VariantsChalk · Clay · Ink
Product informationDescription · Media · Custom fields
ENNLFR
WebshopYour storefront
MobileYour application
APIShared catalog

From product discovery
to the work after purchase.

Build the catalog, cart, customer context, and operational follow-through as one considered journey. Your frontend gives the webshop its identity.

Start with source.
Make the shop your own.

The Next.js storefront starter combines React and TypeScript with an Ominity commerce integration. Inspect its source, adapt the presentation, and validate the complete journey against your own instance.

  • An available Next.js storefront repository
  • Your product presentation and brand experience
  • An adaptable integration, reviewed before launch
Explore starter templates
Next.js storefront · available source
STUDIO / SHOPCollection   Story   Cart

Objects for
everyday living.

The everyday vessel
The studio bowl
The small carafe
Next.jsReactTypeScriptView source
The storefront starter is available. Other template types are planned.

A product page
with the right information.

Use variants, media, localized descriptions, and typed custom attributes to build useful product detail pages. One catalog provides the records; your storefront controls how shoppers compare and choose.

  • Structure variants and their product relationship
  • Add attributes such as material and care instructions
  • Reuse catalog data across connected channels
Explore product information
Catalog · the everyday vessel

The everyday vessel

Example product · VES-001
EN · NL · FR
VariantAttributeInformation
ChalkCeramicProduct variant
ClayCeramicProduct variant
InkCeramicProduct variant
MaterialGlazed ceramic · Custom field
CareDishwasher safe · Custom field
Product media connected to the catalog record

Make the purchase
a deliberate sequence.

Read products, add a cart item, and update or remove it through supported commerce operations. Build validation, empty-cart states, and customer context into the interface around those requests.

  • Connect add, update, and remove item operations
  • Resolve customer context where it is required
  • Handle request errors and rejected actions clearly
Explore commerce
Your interface around supported operations
The everyday vesselExample cart item
Qty 1
POST/commerce/carts/{cartId}/items

Add a product to the cart.

Apply authentication, context, and validation for the operation.

Prepare the collection.
Then prepare its languages.

Write useful source product information and prepare the selected set in multiple target languages. Keep inheritance where the original value should be shared and enable a translation where the market needs its own wording.

  • Use bulk auto translation for a product set
  • Set language-specific descriptions and content
  • Review important names and product claims
Explore ai generation & translation
Source content & language override Nederlands
Headline
Default language (English)

Everyday essentials, made with care.

Using default language content
Need the whole set?

Bulk auto translation prepares selected records in one or more target languages.

Understand the path
through the storefront.

Instrument relevant catalog and cart interactions through the visitor-tracking integration. Choose a small set of useful events, then connect that context to the reporting and services your webshop configures.

  • Connect discovery, product, and cart interactions
  • Keep tracking controlled by your frontend setup
  • Use the events that answer the business question
Explore visitor tracking integration
Interactions with a purpose
Collection viewed/collection
Example event
ContextDiscovery
FrontendWebshop
IntegrationVisitor tracking toolkit
{ event: "collection.viewed", page: "/collection" }

Your implementation chooses its tracking events and when they run.

Webshop journey

The order is a beginning.
Give the next steps a path.

Use events, conditions, and actions for the follow-through you configure around commerce records. Trace the execution and inspect related outbox work when an action needs an external service.

  • Describe the event that starts the workflow
  • Make the matching criteria understandable
  • Inspect action outcomes and external delivery
Explore visual automations
An explicit path to an outcome
Execution
Order createdEvent
First order?Condition
Prepare welcome messageAction
Queue external deliveryOutbox

Follow the event, decisions, and actions.

Explore the details.

The capabilities, examples, and integration choices behind this solution.

A storefront of your own.
A connected commerce foundation.

Start with the available storefront or your own frontend, then connect the catalog and purchase journey around your business.

Let’s talk about
your next project.

Three quick questions to start the conversation.

What’s your name?
Your email app opens a draft at the final step. Nothing is sent automatically.