Everything VeBy does to a product sits between two points: a messy entry in a stockist's billing software, and a clean listing in your app. Four stages connect them.
1. Pull
The connector reads the raw data from the stockist's Tally, Marg, or Busy — product names, HSN codes, MRP, sale rate, GST, and stock quantity. It runs in the background, read-only, and the stockist keeps billing as usual. This is the only stage that touches the stockist's environment, and it touches it as lightly as possible.
2. Standardise
Raw entries are inconsistent across stockists, so the next stage canonicalises them: normalising product names, validating HSN codes, and merging duplicate listings of the same product into one. "SURF EXCEL EW 1KG" from four godowns becomes a single clean product, with the source records still linked behind it.
3. Enrich
A billing line isn't a consumer listing. The enrich stage adds what shoppers need and stockists don't store — clear product images, descriptions, and brand verification — maintained centrally by VeBy. This layer improves over time and applies across every stockist at once.
4. Serve
The cleaned, enriched catalogue is published to the app as a live feed. Price and stock update near-real-time as the underlying billing data changes, so what you see tracks what the stockist actually has. Validation — including the MRP ceiling and HSN/GST checks — gates this final step.
The same pipeline, every city
These four stages don't change from city to city. Point the Pull stage at a new association's stockists and the same Standardise → Enrich → Serve path produces a new city's catalogue. The pipeline is the product; the cities are inputs.