Distributor ERP · in use in Sribhumi, Assam
Manage orders from entry to dispatch.
Your sales staff, owner and warehouse team work from the same order record. Enter retailer orders, approve price changes, prepare loading sheets and send confirmed details to accounts. An FMCG distributor in Sribhumi, Assam uses Sudarshan for this work.
Production records · extracted 25 August 2026.1
Order example · dispatch
The driver leaves the depot at 09:14.
Example order · price request
- Retailer
- Sample Retailer A
- Product
- Ghee 1 L · 24 units
- Request
- 2.5% below list price
Retailers
1,334
retailers in the production records
Orders
10,478
orders staff recorded over 127 days
Routes
23
active delivery routes
Catalogue
1,354
products in the shared catalogue
Average orders per working day
April · initial setup
May–August · 87–92 orders per working day
Staff added 891 retailers in the first six weeks: 106 in the first eight days and 785 in the first full month. From May through 24 August, they recorded an average of 87–92 orders per working day in each month. These figures show use of Sudarshan; they do not measure business growth.
Scroll to view the order example
Order workflow
Use the same order details at each step.
Sales staff enter an order. The owner reviews price requests, and warehouse staff pack the approved items. Billing and dispatch staff continue with the same record.
-
01
Enter the order
Sales staff select the retailer and add products from the current catalogue.
-
02
Review requests
The owner reviews price changes and other exceptions with the order details in view.
-
03
Pack the items
Warehouse staff check the approved quantities and prices before they pack the order.
-
04
Prepare billing
Accounts staff use the confirmed order details for billing and accounting exports.
-
05
Record dispatch
Dispatch staff update loading and departure status. Your team can check it on the order.
Depot tasks
Keep order details current across your depot.
Check an order after the van leaves.
Your team can read the order in Sudarshan while the driver carries a printed loading sheet.
Print loading sheets with current details.
Print from the current order record so warehouse staff can see changes the owner approved before printing.
Review pending price requests together.
The owner opens the approval queue, checks each request and records a decision with the order.
Enter orders from calls or messages.
Sales staff use the same retailer list and catalogue for orders they receive by phone, on paper or by message.
Check the same details across teams.
Packing, billing and dispatch staff use the shared order record to check quantities, prices and status.
Send confirmed details to accounts.
Accounts staff export order details for the billing and accounting process you use.
Owner approvals
Review the price request with the order in view.
The owner can check the retailer, product and requested price in the approval queue. Warehouse staff then work from the order with that decision recorded.
Production results
Review the figures from Sribhumi.
We extracted these figures on 25 August 2026. They cover 127 days at one distributor. The labels separate recorded results from calculations and modeled estimates.
Approval queue
13,469
Decisions the owner recorded in the approval queue.
Piece, price, discount, item, retailer and product requests · 127 days1
11 min
Median time from price request to owner review.
Time between creation and review · 4,038 requests1
Recorded use
64,355
Product lines staff entered across all orders.
Average 6.2 lines per order · largest order 112 lines1
Staff recorded 8,814 packing entries and 20,720 carton movements. They generated 7,202 accounting exports. The notification log contains 45,271 in-app notifications.
Modeled order-entry times
Requirements
Consider Sudarshan if
- You operate an FMCG depot with ₹5–50 crore in turnover.
- You serve 300 or more retailers on several delivery routes.
- You want to keep your current accounting ledger.
- Your owner reviews requests to change prices.
Discuss these needs first
- You need to replace your warehouse-management or accounting software.
- You plan to launch across several countries or legal entities.
- You need customer references. We need customer consent before sharing them.
- You require features beyond those in the current deployment.
Owner review
The owner reviews price changes and other requests in an approval queue.
Shared order details
Your sales and warehouse staff check the same record as your billing and dispatch staff.
Accounting exports
Accounts staff export confirmed details for your billing process.
Customer privacy
We publish totals and percentages. We keep customer details and individual orders private.
Technical review
Check the tests and access controls.
Your technical team can review our test coverage, database checks and session controls. The details below describe the system used at the Sribhumi depot.
637 automated tests
Our engineers run the suite before deploying changes to production. It takes about six seconds.
31 database relationship checks
Our engineers checked 249,306 records and found no broken foreign-key references, such as an order linked to a missing retailer.
Database access controls
Our engineers enable row-level security on all tables. The application uses a designated bypass role to connect.
Separate sessions for four roles
Users can sign in with more than one role on a device. Each role uses a separate session cookie.
Session closure after credential changes
An account holder who changes a credential closes the active sessions that use it.
Live order updates and polling
Staff receive order updates through server-sent events. If that connection fails, the application polls for updates.
Checks on a 9.8 GB migration
Our engineers compared 23 tables, 249,306 rows and 88 numeric column sums before and after a production migration. The checks matched.
Expansion plans
Start with one depot, then review expansion.
One distributor uses Sudarshan in production. We plan to add depots in stages and review each rollout before starting the next. Future locations below are plans.
-
In production
Sribhumi, Assam
The distributor manages 1,334 retailers across 23 routes. The owner reviews exceptions in the approval queue.
-
Planned · next 12 months
Barak Valley
We plan to work with nearby distributors who use similar routes and owner approvals.
-
Planned · later stage
Upper Assam and Guwahati
We plan to assess larger catalogues and businesses with several depots after reviewing the initial rollouts.
-
Planned · longer term
Northeast and other Indian regions
We plan to assess demand from FMCG distributors beyond Assam after the regional rollouts.
Pilot programme
Test Sudarshan with a small team.
We agree on the scope with you before setup. At the end of each stage, you and our team decide whether to continue. You choose a schedule that fits your depot.
-
Stage 01
Review your process
Show us how your team enters orders, approves prices, packs goods and prepares bills.
-
Stage 02
Set up the pilot
We configure the agreed workflow, user accounts, delivery routes and approval rules.
-
Stage 03
Run with your team
Your selected staff use Sudarshan. We track the measures you agreed to review.
-
Stage 04
Review the results
You and our team review staff use and order exceptions, then decide whether to expand.
Book a demo
Show us how your depot works.
We will show you how staff enter an order, review a price request and prepare it for dispatch. You can check whether the process fits your depot before discussing a pilot.
You can email main@skysentinel.co.in, call +91 97302 65133, or speak with our founder on LinkedIn.
Request a demo
Tell us about your depot. We will reply within two working days.
Privacy
You send us your name, company, email address, optional phone number, selected retailer and route ranges, and message. We use these details to reply to your enquiry and continue that conversation. Formspree sends your submission to our team inbox and keeps a copy on its servers in the United States. We do not store submissions on this website. We use no cookies or analytics on the site. To withdraw consent, request a copy of your data or ask us to delete it, contact our Grievance Officer, Tanay Bangale, at cfo@skysentinel.co.in. We aim to resolve requests within 30 days. If you are not satisfied with our response, you can complain to the Data Protection Board of India. SkySentinel Technologies Private Limited (CIN U72100AS2026PTC030972), Guwahati, Assam, is the data fiduciary.
Data sources and method
- Observed. We read production records from the Sribhumi deployment on 25 August 2026. The figures cover 20 April to 24 August 2026, a period of 127 calendar days. We publish totals and percentages without customer details, production order IDs, route revenue or monetary amounts. The animated order uses sample details.
- Derived. We divide each month's order count by its working days for the chart. August covers dates through 24 August. For the approval average, we divide 13,469 decisions by 127 calendar days to get about 106 per day. The 98.3% figure is the share of orders without an invalidation; it does not measure error-free delivery.
- Modeled. We use operating estimates of 15 minutes for manual order entry and 3.5 minutes for entry in Sudarshan. Dividing 15 by 3.5 gives 4.3. We do not have a measured baseline from before deployment or a control group. These estimates do not establish time savings or business growth.