Central Asia Custom Software Development | Custom rules that change without a code change

Challenge

Quotes came from spreadsheet templates, with different prices for different customers and discounts approved over chat. Stock sat in three warehouses and the book rarely matched the shelf. Purchases settled in foreign currency, so margin had to be recalculated by hand after every rate move.

What we delivered

• Quotes and discounts: price lists by customer tier and product line, with approval above a discount threshold
• Multi-warehouse stock: receipts, issues, transfers and counts on one ledger, differences listed for review
• Foreign-currency purchasing: converted at the settlement date, exchange differences shown separately
• Margin reporting: margin by product, customer and order, with a traceable cost basis

Outcome

Quotes are generated from the price list instead of retyped, and discount approvals leave a record. Three warehouses now share one ledger and monthly count differences are reconciled line by line. Margin on foreign-currency purchases converts automatically.

Challenge

Documents for a consignment were scattered across email and shared drives, and declaration packs were assembled by hand. Milestones at the border and beyond were recorded separately, so a customer enquiry meant calling each party. Exceptions had no common log and responsibility was reconstructed from memory.

What we delivered

• Documentation: contract, invoice, packing list and declaration papers collected per consignment, with missing items flagged
• Milestones: inland transport, customs declaration and onward transfer each record time and responsible party
• Exceptions: logged against standard reason codes with photos and resolution
• Customer view: current milestone and history by consignment number

Outcome

Documents are collected per consignment instead of being searched out of email. Each party records its own milestone, so enquiries no longer route through phone calls. Exceptions carry common codes and responsibility is traceable.

Challenge

Raw material was bought by lot, with grade, moisture content and origin recorded on paper. Line issue and output were written by shift, so tracing a lot meant searching files. Machine downtime and output data never met, and capacity was estimated rather than measured.

What we delivered

• Lot records: origin, grade, moisture content and inspection results per lot
• Production tracking: issue, input and output linked by lot, with process milestones recorded
• Machine data: output and downtime signals collected and summarised per shift
• Traceability: raw material origin and customer destination by lot

Outcome

Lot data moved from paper to system, so traceability is a lookup rather than a file search. Issue and output link by lot and loss is calculated per lot. Downtime is summarised per shift.

Challenge

Each store kept its own stock record, so head office could not see same-day sell-through. Replenishment relied on store manager judgement, with stockouts and overstock at the same time. Membership and promotion rules differed per store, and cross-store purchases were not recognised.

What we delivered

• Head office stock: store stock and sell-through summarised daily, with an automatic shortage list
• Replenishment: suggested orders from history, in-transit and safety stock, adjustable by the store
• Store operations: scan-based counting and receiving on mobile, usable offline
• Membership and promotions: rules configured centrally, cross-store purchases recognised

Outcome

Head office sees each store’s stock and sell-through the same day. Replenishment moved from experience to suggested orders. Membership rules are maintained centrally and cross-store spend accumulates.