Engin Sistem
PROJECT CASE STUDY

A Mobile B2B Ordering System for Jewellery

A jewellery producer's WhatsApp-based ordering process became a mobile B2B platform with a catalogue, dynamic pricing and a Logo ERP connection.

Industry Jewellery

Problem

WhatsApp orders were difficult to scale and track; pricing errors increased, and catalogue and ERP processes were disconnected.

System built

A mobile-first B2B platform brought product catalogues, dynamic pricing, order management and ERP connection into one workflow.

Outcome

The system became part of daily operations and continued to be developed. The Turkish case study reports fewer pricing-related returns and shorter order-processing time, using anonymized ranges.

We turned a WhatsApp-based jewellery ordering process into a mobile platform that could be tracked and expanded.

Context and operating conditions

The client is an established jewellery producer with its own production facility and a network across Türkiye. Field sales staff and hundreds of dealers mainly used WhatsApp to ask about stock and place daily orders. The central office processed those messages through spreadsheets and manual entries into Logo ERP.

The problem: an order flow that could not scale

Dealers sent orders and price requests through complex messages.

  • Pricing: Calculating gram-based prices against changing gold and exchange rates by hand led to errors and lost margin.
  • Catalogue: Dealers could request products without knowing whether they were in stock.
  • Disconnected systems: Staff entered approved orders into Logo ERP manually, taking an estimated three to four hours of data entry each day and delaying fulfilment.

Why a standard B2B website was not selected

The initial request was for a B2B ecommerce site where dealers could sign in. A conventional desktop-style ecommerce flow would have been slow for field staff and dealers entering orders while standing in a shop. Sales staff needed to show a catalogue and build a basket quickly during a visit.

We designed a mobile-first, closed B2B ordering network. Dealers could browse the catalogue quickly on a phone. The system calculated gram and purity-based prices using current rates. An API layer between the web system and ERP passed on confirmed orders.

System architecture

  • Mobile-first catalogue: Product images suited to field teams and dealers, with attention to both detail and loading speed.
  • Dynamic pricing layer: A calculation engine applied each dealer’s discount and current rates to base prices from Logo ERP, including gram price, purity and labor.
  • Queued order transfer: If an approved order could not be sent to ERP immediately, a middleware queue retained it and retried the transfer.

Operational result

Teams now place orders through the system, and the catalogue is managed centrally. The Turkish project record states that WhatsApp ordering fell by 90% and returns caused by price-calculation mistakes or incorrect orders fell by 80%. It reports order-processing time moving from 12–20 minutes to 3–6 minutes over six months. These figures are presented as anonymized ranges in the source; they are not a general performance guarantee.

Central-office staff who had entered orders manually moved toward operational monitoring and market development. The system has remained active for years and continues to evolve.

The related jewellery B2B scenario and ERP-connected sales scenario are currently available in Turkish.

Considering a similar system?

Tell us how the process works in your business and where it slows down.

Request a system review

Read the Turkish original →

Measurement preference

Choose whether Google Analytics and Google Ads tags may load in this browser.

Withdrawing permission stops new measurement events. This control cannot retrieve measurements already sent.

Privacy notice