Tonbab
All modules

CRM — B2B sales

A CRM that knows when your customer is due to reorder — because it sees the orders.

Most CRMs guess. Tonbab's reorder-due queue is computed from real order history in the same database. Plan visits with photo + GPS check-in, run deal pipelines including a government-tender board, and convert a won deal straight into a Job Control.

Illustration of the CRM module: accounts, visit plans, pipeline board and the reorder loop

The document flow

Accountshared with opsReorder-duefrom real ordersVisitphoto + GPS check-inDealproduct linesForecaststage-weightedWon → Jobops executesDeliveryfeeds next reorder

How it flows

  1. 1

    Accounts and contacts, shared with ops

    CRM accounts are the same company records your delivery notes and orders already use — one database, so sales sees real purchase history, not a copy.

  2. 2

    The reorder-due queue tells you who to call

    From each account's real purchase rhythm, Tonbab computes who is due — or overdue — to buy again and puts them in a daily worklist. No ML black box, just arithmetic on real orders.

  3. 3

    Plan visits, check in on site

    Set a visit cadence per account. Reps check in with a photo and GPS, then close the visit with an outcome — managers see coverage without chasing reports.

  4. 4

    Work deals on the pipeline board

    Kanban boards with editable stages, including a dedicated board for government tenders. Deals carry product lines with quantities and prices — not just a value guess.

  5. 5

    Forecast on weighted numbers

    Stage-weighted pipeline forecasts and CRM reports management can defend, because the underlying orders and deals are in the same system.

  6. 6

    Win → Job Control → next reorder

    Close-won creates the Job Control that procurement and production execute. The resulting delivery feeds the account's purchase history — which schedules the next reorder-due entry. The loop closes itself.

Product screenshot — coming soon
The pipeline board — deals with product lines, dragged between stages

What ships today

Accounts & contacts

One customer database

CRM accounts are the same records your documents use — no import/export between sales and ops.

Contacts with roles

People at each account with their roles — who purchases, who decides — managed inside the CRM.

Account 360

Every order, delivery, visit, deal and conversation for an account on one timeline.

Field sales

Reorder-due worklist

Daily queue of accounts due to buy again, from real purchase latency — not a guess field sales fill in.

Visit plans with cadence

Set how often each account should be visited and see who is overdue.

Photo + GPS check-in

Reps check in on site and close visits with outcomes — proof of coverage without paperwork.

Pipeline & deals

Kanban boards, editable stages

Drag deals between stages; shape the pipeline to how you actually sell.

Government-tender board

A dedicated pipeline for งานประมูล with its own stages, beside your commercial board.

Deals with product lines

Line items with quantity and price on the deal itself, so value comes from something real.

Weighted forecast & reports

Stage-weighted forecast and CRM reports drawn from the live pipeline.

Closing the loop

Won deal → Job Control

Close-won creates the job that procurement and production execute — no re-keying between sales and ops.

Delivery visibility

Sales sees the deliveries against their accounts without asking ops for updates.

The reorder cycle

Each delivery updates purchase history, which schedules the account's next reorder-due entry automatically.

Who it's for

  • B2B distributors and manufacturers whose revenue is repeat orders from known accounts.

  • Sales teams with field reps who visit customers and need visit proof without extra paperwork.

  • Companies bidding on government tenders that need a separate pipeline for them.

  • Owners tired of a standalone CRM that never matches the numbers in the ERP.

Frequently asked

Where does the reorder-due queue come from?

From each account's actual order history in the same database — Tonbab measures the account's real purchase rhythm and flags when the next order is due. It is transparent arithmetic, not a machine-learning score.

Do we need the Commerce module to use CRM?

No — CRM works from the customer and document history in the operations core. Commerce adds retail channels, but B2B teams can run CRM without it.

Can we change the pipeline stages?

Yes — stages are editable per pipeline, and you can run multiple boards, including a dedicated one for government tenders.

What happens after we win a deal?

Close-won converts the deal into a Job Control — the same document procurement and production work from — so the order sales closed is the order ops delivers.

See it on your own workflows

Book a demo — we set up an organization with your products and walk your team through it.

Book a demo