CBM_GODemo
Moving over

Open work moves over. Old invoices stay where they are.

Every import previews first; every batch undoes whole.

Get a demo with the spreadsheet What it does not do
500
Customer rows a batch
1,000
Shipment rows a batch
What comes across

Four routes in, and what each one promises.

The routeHow it behaves
The customer list
500 rows a batch, matched on customer code.
Open shipments, export and import
1,000 rows a batch, nothing created until previewed.
Rate sheets
CSV, PDF, image or Excel, read twice by the model.
Header aliases
HAWB, H.AWB, hawb no — all read into the same field.
Undo, by the batch
Refused rather than half-done, once anything has moved (Fig. 2).

What stays behind

Historic invoices stay with the existing accounting system.

Why they are not taken

An imported invoice with no history behind it answers no question.

Fig. 2 — Previewed, created, taken back out.Illustrative workflow
Open shipments — export and import Preview 1,000 rows every row shown before one of them exists Create and only now do they exist Undo batch taken back out as one batch The batch comes back out whole every row it made, and nothing else Undo refused 3 of these have been invoiced. Nothing is created until you have looked at the preview and pressed the button. invoiced or already shipped, and the undo is refused rather than half–done
On the way out

Leaving is a menu item.

The shipment list exports in five views, one of them called all.

Export shipments — choose a view CSV
billingfor accounting
customerto send on
opsfor the desk
customsfor the filing
alleverything
The comment on the view
Every field we hold. For migration or backup.

No licence is paid to read the archive.

Taken on the day of signature, or the day of departure.

The full list →

Get a demo

The spreadsheet in daily use is the right one for the call.

CBMGO reads it on the call — known cleanly in ten minutes, not two months.

Get a demoSee the day first