What you can build on EcomWeb
Your online store is just the beginning.
Manage products, prices and checkout once, then use them across your online store, landing pages, mobile apps, AI sales assistants and internal tools. Each new experience connects to the same backend instead of needing a separate system.
Five ways to use EcomWeb
Choose what your team needs to build first.
EcomWeb keeps your commerce data and operations in one place while your team builds the experience or connection it needs.
- Online storeAn online store with a design of your own
- Landing pagesA page of its own for one product or one campaign
- Mobile appsiOS and Android apps on the same data
- AI sales assistantsAdvice and ordering inside the conversation on Zalo, Facebook and website chat
- Data for AI assistantsA product and price source for AI assistants and internal tools
What stays the same
Five ways to build. One shared backend.
The same products, prices and stock across the channels you connect
The same checkout and pricing rules, reused by each new build within what is supported
An API, SDK, CLI and tools for AI assistants to connect anything new to the same backend
Online store
Your own online store, where your team owns the design and EcomWeb handles the data and the orders.
Use your preferred frontend stack and the EcomWeb SDK to bring in products, categories and content. Cart and checkout connect to EcomWeb, so you can reuse the core commerce features instead of building them again.
- Start a project with the CLI on the stack you already use
- Bring in products, categories and content through the API and SDK
- Connect the buy button to the cart and checkout you already have
Landing pages
A page of its own for every product launch or campaign, without building the backend again each time.
Marketing describes the campaign, and an AI coding assistant reads product data and brand assets with the access you allow to build the page. The buy button uses the same checkout as your online store, so the orders arrive in the same list.
- Describe the campaign and let your team or an AI coding assistant build the page
- Bring in the products, prices and live offers from the backend
- Measure with real orders, each one recording where it came from
Mobile apps
iOS and Android apps that share products, customer accounts and orders with your online store.
The app calls the same API your online store already calls, so there is no second system to keep in sync. Wherever a customer orders, the order arrives in the same list under the same customer.
- Call the same API your online store already uses
- Share accounts, carts and order history with the online store
- Change a price or a product once and let the app follow
AI sales assistants
Customers can get advice and start an order inside the conversation on Zalo, Facebook or website chat, instead of only getting an answer.
The assistant calls the EcomWeb API to find products, check current prices and offers, then create a cart and open a secure payment link. Prices and offers are checked again before the order is created, so an assistant cannot offer a deal outside your rules.
- Advise with product information your business has approved
- Create a cart and start checkout inside the conversation
- Hand over to a person when something falls outside the access you allowed, with the conversation attached
Data for AI assistants
AI assistants and internal tools you have given access to read the same approved products, prices and stock.
Instead of copying your catalogue into every tool, each assistant or system reads it directly from the backend through the API and the tools for AI assistants. Access permissions are separate for each one, so adding an assistant does not open up everything.
- Give each assistant or system its own access permissions
- Read approved products, prices, stock and product guidance
- Withdraw or narrow one set of permissions without touching the rest
Where it can go from here
- Ordering portals for resellers and business customers
- CRM, ERP and marketing tool sync
- More messaging channels as suitable connections arrive
- An activity log for each set of access permissions
Where to start
It depends on what your team needs now.
New to selling online
Start with the online store, then add a landing page for each launch.
Marketing teams
Start with landing pages, then extend to an AI sales assistant in messaging channels.
Engineering teams and agencies
Start with the API and SDK, then reuse the same connection for online stores, apps and later projects.
Operations teams
Start with the AI sales assistant and the shared data source, to cut manual answering and lookups.
Next step
Start with what you need to build first.
Create a free store to work with real data, or look at the API, SDK and CLI before your engineering team starts.