Oriental Nippon Development
Back to portfolio
Case studySupplier to restaurants, cafés and bars

B2B Ordering Platform and Mobile App for a Hospitality Supplier

Orders came in by phone, email and sales reps, so growth scaled with headcount. We built a B2B platform with customer-specific pricing, wired straight into the ERP, plus an app shop owners can order from between service periods.

Industry
Retail & E-commerce
Region
Germany
Engagement
Lab-type ODC (dedicated team)

Outcomes

  • Self-service ordering 24/7
  • ERP-native pricing & stock
  • Growth decoupled from sales headcount

Stack

Odoo · Python · Mobile app · PostgreSQL · CI/CD

Written byOriental Nippon Team

A German supplier sells to independent restaurants, cafés and bars across a regional market. Its customers are small, numerous, and order often in modest quantities.

Serving them through sales reps was expensive, and serving them badly meant losing them to a larger distributor. Growth was tied directly to how many reps the business could afford.

The problem

  • Ordering by phone and email. Every order went through a person.
  • No self-service. Customers could not see their own prices, order history or stock availability without asking.
  • Growth tied to headcount. More customers meant more reps.
  • Re-keying. Informal orders were typed into the operational system again.
BeforeAfter
How shops orderedPhone, email, repsWeb platform and mobile app
Customer pricingAsk a repShown per customer
Order entryRe-typed by staffFlows straight into Odoo
ReachLimited by rep visitsNot tied to sales visits

What we built

  • A B2B commerce platform

    Customer-specific pricing, availability, ordering and order history, with Odoo as the source of truth.

  • A companion mobile app

    For shop owners, so an order can be placed in the two minutes between service periods.

  • A direct order flow

    A customer order becomes an operational transaction with no transcription.

  • Release pipelines

    CI/CD for both the platform and the app.

An order from a shop owner, start to finish:

Technology and the role it played

TechnologyRole in this project
OdooSource of truth for pricing, stock and orders
PythonPlatform services and integrations
Mobile app frameworkThe shop-owner app, built on the platform API
PostgreSQLOperational data
CI/CDRoutine releases for platform and app

How we delivered it

Discovery included the trade customers themselves, not only the supplier, because they were the ones who would decide whether to use it.

  1. Discovery with customers. How shop owners actually order.
  2. Foundation. Environments, pipelines, catalogue and pricing structure.
  3. Platform. Catalogue, customer pricing, ordering and history.
  4. Mobile app. Built on the platform API and tested with real shop owners.
  5. Pilot cohort. A group of real customers ordering for real.
  6. Roll out and iterate. Based on how the first cohort used it.
Delivery timelineIndicative total: 15–20 weeks
  1. 01Discovery

    2 wks

    Customer behaviour, catalogue and pricing structure

  2. 02Foundation

    2 wks

    Environments, pipelines, data model

  3. 03Commerce platform

    5–7 wks

    Catalogue, pricing, ordering, order history

  4. 04Mobile app

    4–6 wks

    Native app on the platform API, field-tested

  5. 05Pilot cohort

    2–3 wks

    A group of real customers ordering for real

  6. 06Roll-out

    ongoing

    Customer segment by segment

Risks and how we handled them

RiskHow we handled it
Building what the supplier wants, not what shops useDiscovery included the trade customers themselves
An app that fails in a busy kitchenField-tested with real shop owners
Low adoption at launchA pilot cohort of real customers before general availability

Outcome

Trade customers serve themselves, at the hours they actually work, against their own prices. The supplier can reach more shops without a sales visit for each one.

The client reports better customer satisfaction and wider market reach. We have not measured either independently, so we report them as their observations, not our claims.

What the client keeps

  • Platform and mobile app source, in their own repositories
  • The catalogue and pricing model
  • Deployment pipelines
  • Integration documentation

Sources and further reading

  1. Odoo 17 documentation, Odoo
  2. The Twelve-Factor App, 12factor.net

Facing something similar? This is the kind of work our Software Engineering & Cloud team delivers every day. Talk to us about your stack.