Verity for e-commerce
E-commerce margin survives or dies after the order. Verity records the return, the failed delivery and the marketplace deduction against the order that produced them.
Verity runs operations. Your online store and marketplaces stay where they are.
Verity / Operations
LiveOrders shipped
9,840
Return and RTO rate
14.2%
Settlement variance
₹4.6 L
Stock out of sync
86 SKUs
Needs attention
Illustrative figures. Verity shows your own operations in this shape.
How the business runs
An e-commerce business sells across its own site and several marketplaces, each with its own inventory feed, its own fulfilment expectations, its own return rules and its own settlement arithmetic. The order is captured cleanly. What happens afterwards — returns, failed deliveries, marketplace deductions, customer service — is where the margin actually goes, and it is recorded in as many places as there are channels.
Returns and return-to-origin are the largest of these. A return costs the outbound shipping, the return shipping, the handling and often the saleability of the item, and it is concentrated: particular categories, particular sizes, particular descriptions, particular regions and payment modes. A business that records returns as a total cannot see the concentration and therefore cannot act on it.
Marketplace settlements are the second. Payouts arrive net of commissions, shipping, penalties and adjustments, and reconciling them against the orders they cover is a monthly chore that most businesses do partially. Four point six lakh of unreconciled deductions across three cycles is money that was possibly deducted incorrectly and will never be recovered.
The third is inventory across channels. Stock sold on one channel must reduce availability on the others, and a lag produces oversells, cancellations and marketplace penalties.
Verity records the order, its returns, its shipping outcomes and its settlement against one set of stock and one customer.
What Verity calls these things
What gets in the way
E-commerce difficulties are all downstream of the order, in returns, delivery failures and settlements.
Returns are recorded as a rate, not a cause
Return rate is known in total, so the concentration by category, size, description or region that would let you fix it is invisible.
In Verity Returns carry reasons and attach to the SKU, listing, region and payment mode, so concentration is visible.
Settlement deductions go unreconciled
Payouts arrive net of commissions, shipping and penalties, and matching them to orders is partial at best.
In Verity Settlements reconcile against recorded orders, so unexplained deductions become claims rather than losses.
Channel stock drifts and produces oversells
A sale on one channel must reduce availability on the others, and lag causes cancellations and marketplace penalties.
In Verity One stock position across channels, with allocation and sync state visible per SKU.
RTO cost is absorbed as shipping
Failed deliveries cost outbound and return freight and are recorded as a general shipping expense rather than against the pattern that caused them.
In Verity RTO is recorded against the order, region, payment mode and courier, so the concentration is addressable.
Customer service load is unattributed
Tickets are handled without being connected to the orders, SKUs or listings that generate them.
In Verity Service contacts attach to the order and SKU, so the products creating the load are identifiable.
Fulfilment commitments differ by channel and are managed as one
Each marketplace has its own dispatch expectations and penalties, and the warehouse works one queue.
In Verity Channel commitments are on the order, so the queue is worked by deadline rather than by arrival.
The complete system
One system across channels, stock, fulfilment and settlements.
Orders
Each order records its channel, items, customer, payment mode, fulfilment commitment, shipping outcome and any return with its reason.
Why it matters here The order is where revenue and every downstream cost meet, and the downstream costs are usually recorded elsewhere.
In practice Return rate at thirty-one percent on one category, with the recorded reasons naming the cause.
Inventory
Stock is held once with allocation across channel listings, reservation on order and sync state per channel.
Why it matters here Overselling is a stock-synchronisation failure, and it costs cancellations and marketplace standing.
In practice Eighty-six SKUs out of sync across channels, flagged before they cause cancellations.
Work
Fulfilment is work with a deadline derived from the channel commitment, an owner and a state.
Why it matters here Each channel penalises late dispatch differently, so the queue should be worked by deadline rather than by order of arrival.
In practice The dispatch queue ordered by channel deadline rather than by when the order came in.
Suppliers
Channels, couriers and suppliers are relationships with their terms, performance, deductions, penalties and balances.
Why it matters here A marketplace is a supplier of demand with commercial terms, and a courier’s failure rate is a direct margin cost.
In practice RTO rate by courier and region, which changes routing decisions.
Workflows
Settlement reconciliation, deduction disputes, penalty claims and refunds move through defined steps with recorded outcomes.
Why it matters here Deductions are frequent, individually small and collectively significant, and they expire if unclaimed.
In practice Four point six lakh of unexplained deductions raised as claims rather than absorbed.
Relationships
Customers are records with their orders, returns, service contacts and lifetime value across channels.
Why it matters here The same customer buys across channels, and return behaviour and service load are customer-level facts.
In practice Customer lifetime value net of returns, which is a different ranking from gross revenue.
Communication
Customer contacts, complaints and resolutions attach to the order and SKU they concern.
Why it matters here Service load is generated by specific products and listings, and connecting the two is how it reduces.
In practice Contacts concentrated on one listing whose description is misleading.
Locations
Locations and channels roll into the business, with stock, fulfilment and reporting following the same structure.
Why it matters here Regional patterns in RTO and delivery failure are among the most actionable facts in e-commerce.
In practice RTO concentrated in one region and payment mode, quantified as absorbed shipping.
Reports and analytics
Contribution after returns, shipping and deductions; return concentration by cause; settlement variance; fulfilment against commitments; and service load by SKU come from the operational records.
Why it matters here Gross revenue by channel is easy and misleading. Contribution after everything downstream is the real number.
In practice Contribution by SKU after returns, RTO and settlement deductions.
Verity AI
Verity AI answers from your own order, stock, return and settlement records, respects permissions, and can create assigned follow-ups.
Why it matters here The questions that matter cross channel, product, region and courier at once.
In practice "Where are returns concentrated and why?" returns the categories and reasons with actions assigned.
People
Staff are modelled once, and every pick, pack, dispatch and service contact carries who handled it.
Why it matters here Picking accuracy is a direct driver of returns, and it is a per-person number.
In practice Returns attributable to picking errors, by person and shift.
Control
One permission model and one audit trail across every record.
Why it matters here Refunds and goodwill credits are issued under service pressure and add up.
In practice Refunds beyond policy recorded as approvals with the order history attached.
Work in motion
These already happen across channels. On one record the downstream costs become attributable.
Working the queue by channel deadline rather than by arrival order is what avoids penalties.
The reason is what turns a return rate into an addressable cause.
RTO concentration by region and payment mode is one of the most actionable patterns in e-commerce.
Deductions are small individually and material together, and they are only recoverable within a window.
An oversell costs a cancellation, a penalty and marketplace standing, all avoidable.
Service load is generated by a small number of products, and fixing the listing is cheaper than answering the tickets.
Verity AI
Verity AI reads the same order, stock, return and settlement records the business creates as it trades. It answers from your own channels, respects permissions, and can turn an answer into claims and actions.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the order and stock records at the point the condition is met.
When
A settlement is received
When
A return is recorded
When
A delivery fails
When
Channel stock drifts out of sync
When
An order approaches its channel dispatch deadline
When
Service contacts concentrate on a listing
What you can understand
Contribution after everything that happens downstream of the order.
Verity records operations. Your online store, marketplace integrations and payment processing continue as they are.
One system, different ways of seeing it
Everyone works from the same records, and each role opens on what they need.
Founder
What is actually profitable?
Contribution by SKU and channel after returns and deductions, RTO concentration, settlement realisation.
Operations manager
What is at risk today?
Orders against dispatch deadlines, stock sync, returns to process, courier failures.
Finance
Are the settlements right?
Settlement reconciliation, unexplained deductions, claims raised and recovered, refunds issued.
Catalogue and service
Which products are causing the load?
Contact volume and return reasons by listing, description and sizing issues, actions taken.
Where it is used
Reasons recorded against SKU, listing and region, so a return rate becomes a concentration you can act on.
Payouts matched against recorded orders with deductions verified against terms, so unexplained amounts become claims rather than losses.
One stock position with allocation and sync state per channel, preventing the oversells that cost cancellations and standing.
Failed deliveries recorded by region, payment mode and courier, exposing one of the most actionable patterns in the category.
The dispatch queue worked by channel commitment rather than by order arrival, avoiding penalties.
Contribution by SKU after returns, shipping and deductions, which is a different ranking from gross revenue.
Contacts attached to orders and SKUs, so the small number of listings generating most of the load can be fixed.
Plain-language questions across returns, settlements, stock and couriers, with claims and actions raised in the same step.
Getting there
Your online store, marketplace integrations and payment processing continue to run and are mapped during implementation. SKUs, channel listings, stock, open orders, returns and settlement history are brought across, and Verity is introduced as the operational layer.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own order, stock, return and settlement records: where returns are concentrated and why, which marketplace deductions are unexplained, which SKUs are out of sync across channels, where RTO concentrates by region and payment mode. Each answer can become a claim or an action.
No. Your online store, marketplace connections and payment processing continue and are mapped during implementation. Verity records operations — stock across channels, fulfilment, returns, RTO, settlements and service load.
Returns carry a recorded reason and attach to the SKU, listing, region and payment mode, so a return rate resolves into concentrations — a category, a size, a misleading description — that can actually be fixed.
Settlements are matched against your recorded orders and returns with commissions, shipping and penalties verified against channel terms, so unexplained deductions become claims raised inside the window rather than money quietly absorbed.
Stock is held once with allocation and reservation across channel listings and sync state monitored per SKU, so drift is flagged before it produces a cancellation and a marketplace penalty.
Contribution is calculated by SKU after returns, shipping, RTO and settlement deductions, which frequently produces a very different ranking from gross revenue by product.
Service contacts attach to the order and SKU, so the small number of listings generating most contacts is identifiable — and fixing the listing is considerably cheaper than answering the tickets.
Warehouses, channels and regions are locations rolling into the business, so allocation, dispatch performance and delivery outcomes are visible per location.
About four weeks: discovery and mapping of channels, fulfilment commitments and settlement terms, configuration, migration of SKUs, stock and open orders, then an ongoing operations partnership.
Both are margin already lost that most operators cannot break down. Tell us which is bigger for you.