The website is a separate business
Your storefront platform keeps its own catalogue, its own stock and its own customer list, and reconciling it with the warehouse is somebody's full-time job.
From the production line to the customer, one dataset.
A D2C brand runs two businesses at once: making or sourcing stock, and selling it direct online. VAP holds both on one dataset — production and warehouse stock on one side, your own storefront and marketplace channels on the other — so a unit made this morning is sellable everywhere this afternoon, and no channel oversells the last one.
What gets in the way
Your storefront platform keeps its own catalogue, its own stock and its own customer list, and reconciling it with the warehouse is somebody's full-time job.
Listing the same inventory in two places without one source of truth guarantees an oversell on the weekend a campaign works.
Raw material, production and landed cost live outside the system, so contribution margin per SKU is calculated monthly rather than known.
What you get
Production units and warehouses are sites of their own, with recorded transfers between them.
Size, flavour, pack and bundle are variant options, each with its own stock, price and cost history.
Vritti builds and deploys a Next.js and Payload CMS store reading live catalogue and stock — not a second catalogue.
Your own store, marketplaces and retail each get a catalogue and price per channel, from one stock position.
Cost tracked per unit through receipt and production, so contribution margin per SKU is a fact not a monthly exercise.
The shopper on your site is the same party your team sees internally — history, returns and messages together.
Food, supplements and cosmetics carry lot and expiry tracking with FEFO picking.
Invoices, credit notes and GST reports per registration, from the same records.
In practice
Your store and every marketplace channel draw from one stock position, so a spike in orders cannot promise units that no longer exist.
Create the variant once. It appears in production planning, warehouse stock, your storefront and every channel priced for that channel.
Cost captured at receipt and production means contribution margin is available per variant, not reconstructed at month end.
The apps behind it
Online
Vritti builds the storefront and deploys it on Vritti Cloud, on your own domain. Connecting it to VAP is optional — but when it is connected, there is one catalogue and one inventory instead of two.
Vritti builds your store on Next.js and Payload CMS and deploys it on Vritti Cloud, on your own domain, reading live data from VAP through the core SDK.
Content, images and copy are editable in the CMS beside a live preview of the real site — no developer needed for a price or a paragraph.
FAQ
Yes. Production units and warehouses are sites in the same inventory model your storefront reads from, so a unit produced and received into the warehouse becomes sellable online without a sync step.
No. Vritti builds your storefront on Next.js and Payload CMS reading the catalogue, variants, prices and stock live from VAP through the core SDK, so there is one catalogue rather than two that drift apart.
Yes. Sales channels each get their own catalogue and pricing per site, drawing from one stock position. The same product can carry different prices per channel without duplicating inventory.
No. The VAP integration is optional. You can run VAP for operations and keep your existing storefront, or have Vritti build and deploy the storefront for you — the integration is what connects them.
Yes. Cost is tracked per quant through goods receipt and production, so contribution margin can be seen per variant rather than reconstructed from a spreadsheet at month end.
Get started
Tell us what you sell, how many outlets and registered firms you run and where you sell. We will walk you through a real system set up like yours — not a generic demo.