Retail
Build a working commerce product from a prompt.
Describe the business and let Build create the brand, pages, catalogue, checkout, till, and operating configuration in one editable workspace.
Merchant brief
A bakery in Yaba with collection, delivery, card, and transfer.
I prepared the catalogue, checkout, website, and staff roles for review.
Describe a change ↑
Yaba BakeryShop About Basket 0
Fresh every morningBread made for the neighbourhood.
PromptDescribe the product and keep refining it through conversation.
CanvasPreview every surface and edit the generated result directly.
Commerce runtimePublish onto real catalogue, order, and customer records.
Connected from the first draft
One build. Five working products.
Start from a prompt or pattern
Do not begin with an empty canvas.
Describe the product from scratch or begin with a proven commerce shape, then let the builder assemble a first working version.
Food
Menu, modifiers, service.
Services
Availability, resources, bookings.
Built around the real business
Start with how the merchant sells.
Build turns the merchant brief into a connected experience for customers and staff, then leaves every generated decision open for review.
AI starts the work
The merchant still owns the result.
Build shortens the distance from an idea to a working business. It does not hide the catalogue, pages, settings, or permissions behind a generated layer. Every result remains visible and editable.
- Use the generated product before publishing it.
- Change a single field or describe a broader revision.
- Return to an earlier version when the new direction is wrong.
One building workspace
From idea to live commerce.
Natural language brief
Explain the product you want.
Name the business, its customers, what they should be able to do, the channels it needs, and how the brand should feel.
Working generation
Receive more than a landing page.
Build creates connected pages, catalogue data, checkout rules, till configuration, and permissions on Commerce Engine.
Prompt and visual control
Change it by describing or selecting.
Ask for a broader change through conversation, or select generated content and adjust it directly in the workspace.
Responsive preview
Test each surface, then publish.
Review the experience at different sizes, approve the version, and publish through the normal platform release path.
One brand, every surface
Generate the system, then tune every detail.
Build creates a reusable visual language and applies it across the merchant website, checkout, and till. Change the shared foundation or refine one surface where its job is different.
Brand foundation
TypeNeighbourhood Grotesk
Colour
ShapeSoftSquare
From page to operation
A beautiful draft that can already take an order.
Checkout arrives connected.
Products, prices, customer context, collection, delivery, and installed payment methods are real engine configuration from the first preview.
The work after payment is included.
Build proposes the fulfilment states, location rules, opening hours, and staff access needed to complete what the customer bought.
The second build matters more
Rebuild without resetting the business.
Orders, customers, and stock belong to Commerce Engine, not to the builder. A merchant can replace structure and presentation later while live trading history remains intact.
See the engine underneathClear responsibility
Build proposes. People decide.
Merchant approval
Nothing is published until the merchant has reviewed the proposed business state.
Institution approval
Identity, sanctions, risk appetite, and permission to trade remain institution decisions.
Licence boundary
Build can configure only the packages installed for the deployment. It cannot invent missing capability.
Build questions.
Does Build create a separate website project?
No. It writes editable configuration used by Website, Merchant Console, Retail Rails, and Commerce Engine.
Can a merchant change generated work?
Yes. Generated values become ordinary product state and can be edited directly in Merchant Console.
Does rebuilding erase live records?
No. Orders, customers, payments, and stock remain owned by Commerce Engine.
Does Build approve a merchant to trade?
No. The institution owns verification, approval, and every regulated decision.