Boxed 1C (Trade Management, Small Firm, or ERP) tracks stock balances — and for many companies that’s where its “warehouse” ends. Once you have more than 500 SKUs, 2+ locations, or your first wholesale client, problems pile up. Below are the five customizations we build most often for trading and wholesale companies in Uzbekistan.
1. Cell-based storage
Without cells, a new stock keeper spends half a day figuring out where things are. At scale this becomes a systemic cost.
What we build: split the warehouse into cells (e.g. A-12-3 — rack A, section 12, shelf 3), tie stock balances to cells, and add optimal-route picking for orders.
| Without cells | With cells |
|---|---|
| Newcomer trains 2 weeks | Newcomer works day one |
| Order pick — 25 min | Order pick — 8–12 min |
| Inventory count — 2 days | Inventory count — 4 hours |
2. Handheld scanners (data terminals)
Keyboard-entering SKU codes means errors and slow operations. A modern warehouse runs on scanners — handheld terminals (Zebra, Honeywell, Chainway) or smartphones with our mobile client.
What we build: an Android/Windows CE client that talks to 1C over HTTPS. Receiving, shipping, inventory counts, transfers — all through barcode or QR scans.
Outcome. Picking errors drop to a handful per month. Warehouse operations run 2–3× faster.
3. Integration with Uzum Market and other marketplaces
Selling on Uzum Market, alif shop or mymarket.uz by hand is unworkable: stock doesn’t sync, orders land in a separate admin panel, shipments have to be marked in two places.
What we build: two-way API integration:
- stock and prices → to the marketplace every 15 minutes;
- orders → into 1C with immediate reservation;
- shipment statuses ← back to the marketplace.
// example scheduled job — stock sync every 15 minutes
ScheduledJob_UzumSync.RepeatInterval = 900; // seconds
ScheduledJob_UzumSync.UseQueue = True;4. FEFO for perishable goods
FEFO (First Expired — First Out) ships batches with the nearest expiry first. Critical for food, pharma, cosmetics, chemistry.
What we build: batch-picking algorithm by expiry date instead of FIFO, automatic alerts at 30 / 14 / 7 days before expiry, and a “Stock at write-off risk” report.
Without FEFO. A typical food distributor loses 0.8–2% of turnover monthly to write-offs. With FEFO — 0.1–0.3%.
5. Order reservation with priorities
When 30 orders come in at once and stock isn’t enough for all — who gets served first? Standard 1C leaves this to gut feel.
What we build: a reservation module with rules — VIP clients → retail → B2B by payment date → everyone else. Managers see what’s actually free now and what opens up after a specific shipment.
Case snapshot
“BarkatTex,” a Tashkent wholesale fabric distributor. 4,000 SKUs, 3 warehouses, 60 orders a day.
Before: a “reservations” Excel on the bookkeeper’s laptop, order pick — 25 min, mis-picks 2–3 times a week.
What we did: cell storage + handhelds + reservations (items 1, 2, and 5 above). 5 weeks of work.
After: order pick — 9 min, mis-picks — 1–2 per month, order throughput up by 40% without adding staff.
Frequently asked
Do we need 1C:WMS or is Trade Management enough? In 80% of cases a customized Trade Management or ERP is enough. 1C:WMS only pays off for very large warehouses (5,000+ m² and 10,000+ SKUs).
Which handheld should we pick? For a start — budget Chainway or Urovo (from 2.5M som). For harsh conditions (cold, dust) — Zebra TC22/TC27. Our client works with any Android 8+ device.
How long does it take to roll out all 5 customizations? 6 to 12 weeks depending on scale. Minimum setup (cells + handhelds) — 3 weeks.
Will Trade Management updates break the customization? No — we write through configuration extensions and regression-test on every new version.
Free warehouse audit. We’ll visit or jump on a call, look at where time and money leak, and give you a customization plan with timing and cost in 30 minutes.
Also read: 5 things standard 1C:Payroll can’t do for Uzbek companies, custom 1C in Uzbekistan.
