OI / CI flow

Give the order → the tool sets it up → you review. ⬇ Download blank order form — horizontal, one row per printer

1 Give order

2 Tool: OI

3 Team review

4 Tool: CI

5 Approve

Contract Master — upload once; remembered for every step & order until you change it

Import order — any format, all at once — add EVERY file (Excel, mail .eml/.msg, PDF, WhatsApp screenshot) — they STACK, add as many as you like — and paste any WhatsApp/typed orders below. One Extract reads them all into one draft.

Drop or click to add Excel / .eml / .msg / .pdf / WhatsApp screenshot — add several, one per customer; each new pick is added, not replaced

…and/or paste WhatsApp message(s) / mail body (type a phone-call order here too):

Company name (optional — use only if the mail doesn’t name the customer; applied to rows left blank)

↑ Filled the downloaded sheet? Re-upload your completed Order Sheet here to process it →

Completed Order Sheet — drop the Order Sheet you downloaded & filled here to process. (It also auto-fills from the Order draft above if you'd rather edit inline — either way, one file feeds Steps 2–4.) Customer — optional; auto-detected from the sheet. Only pick as a fallback. Billing type — auto-filled from the Contract Master; change only to override how NEW ledgers are named

Step 2 · Detect read-only preview of what will be created — optional

Step 3 · Generate Tally files Ledger → DN → Contract — do this FIRST, import into Tally, then create the ticket in Step 4
Billing code (from Tally after ledger import; blank for new ledgers)

DN dispatch rates (Printer = the BOX-PACK printer price, Cartridge = the cartridge price — what the DN / challan should show; per batch, leave blank to skip)
(rate × qty — qty blank = 1)
Printer × Cartridge ×

Show other part charges (Trolly, USB, Stabilizer, ADF, …)

Trolly × Stabilizer × USB Hub Kyocera 2040 × USB Cable × Power Cable × Konica Minolta ADF × Wi-Fi Card × Card Reader × SSD × Additional Tray ×

DN date DN start no — the FIRST DN number, exactly as it reads in Tally (the prefix is taken from what you type). Type a plain number to keep the default prefix.

Contract start no — the next free contract no in Tally today. Leave blank to use the CM (only safe if the CM is fresh — contracts made since it was extracted won't be counted).

Ledger file DN file

Import: Ledger → Import Masters → Excel with Behaviour if master exists = Modify (Ignore leaves an existing/stub ledger blank); DN → Import Transactions → Excel. The ledger's extra rows with only an Address are the address's 2nd/3rd lines — don't delete them. The company group must already exist in Tally. A branch added to an existing ledger comes as a separate address-types XML.

Step 4 · Create ticket + database after the Tally ledger/contract are imported — the ticket references the billing code
Database (Company+Branch + Contact) Printer+Serial OI ticket
Create all the way through — after each OI is created, automatically create its CI + PI child tickets too (Dispatch Date = today, printer tested = Yes; edit on the PI card if needed). Skips the separate approve step — use for clean orders.
Order approval + PO (the order message / WhatsApp screenshot / PDF / Excel — and the PO file if you have one — all attach to the OI’s “Upload Current Order Approval”. Add files one at a time from any folder — each pick is added, not replaced — and all of them attach (the order + the PO together). Multi-customer batch: each file goes to the customer named in its filename.)
Delivery Note (Non-Signed) — optional (the DN PDF / scanned copy you have — attached to the OI’s “Uplode Delivery Note (Non Signed)”; leave blank to attach later)
— Create 1 test ticket makes ONE order first; review it in Pipefy, then Create ALL does the rest (the test ticket is reused, not duplicated). If any required field is blank you get ONE box — fill it or Proceed anyway.

OI / CI dispatch flow build 2026-08-03-z170