Skip to main content
Haichuang Global Haichuang Global Technology Services for Global Chinese Businesses
Case Library

Central Asia case library: 5 projects across 5 industries

A consolidated record of delivery practice in Central Asia. Each entry states the project name, client background, industry, business challenge, deliverables and delivery value. Cases can be filtered by industry or by service.

Trade & wholesale Custom Software Development Business System Development

Building materials and machinery trading system

Client: A building materials and machinery trader (cross-border wholesale, about 12,000 orders a year)

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.

Delivery value: Product, customer and price data become queryable records, so quoting and purchasing decisions have a basis. Finance spends less time on manual reconciliation.
Food wholesale Business System Development Mobile App Development

Agricultural and food wholesale order and delivery system

Client: A food and agricultural wholesaler (four cities, more than 200 stores)

Challenge

Orders arrived by phone and chat, each salesperson kept their own record, and both duplicate and missed orders occurred. Delivery routes were left to driver experience although fresh produce has tight time windows. Returns followed no common code, so month-end reconciliation was disputed.

What we delivered

  • Order intake: phone, chat and store self-service orders enter one queue
  • Picking and delivery: pick lists and delivery notes by category and route, visible to drivers
  • Returns: logged against reason codes and linked to the settlement statement
  • Reconciliation: statements per store, with every difference annotated

Outcome

Duplicate and missed orders stopped. Routes are planned by order volume and delivery windows for fresh produce are controllable. Returns carry standard reason codes and reconciliation disputes fell.

Delivery value: Order and store data show category mix and repeat purchase, giving purchasing a basis for planning. Delivery timing data supports capacity assessment.
Logistics & fulfilment Custom Software Development Business System Development

Customs clearance documentation and milestone tracking

Client: A cross-border logistics provider (about 6,000 consignments a year)

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.

Delivery value: Every consignment has a complete record, which settles disputes. Timing data per border crossing and lane supports quoting and scheduling.
Manufacturing Custom Software Development IoT Development

Cotton and textile procurement and production tracking

Client: A textile manufacturer (three production lines, about 4,000 tonnes purchased a year)

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.

Delivery value: Lot data across raw material and finished goods shows grade mix and loss, informing purchasing. Capacity data supports production scheduling.
Retail chains Custom Software Development Mobile App Development

Retail chain store and warehouse integration

Client: A retail chain (18 stores, food and household goods)

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.

Delivery value: Store and category data show turnover and mix, informing range and promotion decisions. Count differences form a list, reducing finance reconciliation effort.

Case note: client names are anonymised under confidentiality agreements; cases are presented to explain implementation approach and delivery boundaries, and specific figures are subject to project acceptance records.

Call us