LineNow
ProcurementInventorySuppliersResources
LoginBook a Demo
LineNow
  • Suppliers
  • Pricing
Login
Book a Demo
Blog/Buyer Insights
Case StudyOperator playbook

How Whitmans Cut Supplier Back-and-Forth From 8 Rounds per PO to 1 in 8

Whitmans cut supplier back-and-forth from 8 rounds per purchase order to one round in every 8 POs — a 64-fold reduction in threads buyers have to read, interpret, and retype.

Jainul Vaghasia/Published July 4, 2026/4 min read

For operators

Use this playbook to tighten the buying loop.

LineNow helps teams move from manual ordering and supplier follow-up to a connected workflow for POs, receiving, inventory, and accounting handoff.

View Ecommerce Inventory WorkflowsSee How LineNow Works

Contents

  1. What 8 rounds per PO actually costs
  2. What changed
  3. The math
  4. The takeaway for multi-supplier retailers
Back to top

"The LineNow team is extremely pro-active about your success with PO and inventory-aware ordering. We researched many PO and inventory apps that are available, most of them are 'cookie cutter' type apps that force you to be limited on what features you will have access to. Not this one. You will not be disappointed!"

— Ralph W., Whitmans


Whitmans is a multi-location retailer that orders across a large catalog from many suppliers. Before LineNow, the average purchase order took about 8 rounds of back-and-forth with the supplier — confirmations, price corrections, stock questions, substitutions, ETAs. Today, a back-and-forth happens roughly once every 8 purchase orders.

That is a 64-fold reduction in supplier threads a buyer has to read, interpret, and act on. These are Whitmans' own numbers, and this page explains what changed.

What 8 rounds per PO actually costs

The rounds themselves were never the whole cost. Each exchange meant:

  • A buyer reading the reply, working out what it changes — price, quantity, timing — and retyping the consequence into notes or a spreadsheet
  • The purchase order going stale between rounds, so nobody could trust the document itself; the email thread became the real system of record
  • Receiving and accounting inheriting whatever the thread said last, whether or not anyone transcribed it correctly

Multiply 8 rounds by every PO, every supplier, every location, every week, and the ordering workflow spends most of its time on conversation management instead of buying.

What changed

The back-and-forth collapsed from both ends:

  • POs go out right the first time. LineNow attaches each supplier's pack sizes, minimums, and current pricing to the order before it's sent — so the questions suppliers used to ask ("that comes in cases of 12," "price changed last month") don't need asking.

Read before ordering

A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.

  • The replies that do come stop being homework. Confirmations, shortages, substitutions, price changes, and ETAs are read by LineNow into reviewable updates on the order itself. The buyer approves the change; nobody retypes an email.
  • The PO stays current, so nobody re-asks. Because the order record absorbs every reply, the team stopped pinging suppliers for status they technically already had — and suppliers stopped re-explaining things the thread had already said.
  • Before LineNowAfter LineNow
    ~8 rounds of email per PO~1 round of back-and-forth per 8 POs
    Packs, minimums, and prices confirmed by emailAttached to the PO before it's sent
    Replies retyped into notes and spreadsheetsReplies become reviewable updates on the order
    Email thread is the system of recordThe purchase order is the system of record
    Invoice surprises found at month endReceiving and pricing reconciled on the order

    The math

    Eight exchanges per PO down to one exchange per eight POs is 8 → 0.125 — a 64× reduction per purchase order.

    That number compounds in a way time savings alone don't. Time spent building orders scales with the catalog; time spent chasing replies scales with everything — supplier count, order volume, and how often prices move. A buyer managing 8× the volume with the old workflow drowns; with the reply load cut 64-fold, order volume can grow without the inbox growing with it.

    The takeaway for multi-supplier retailers

    Count the rounds of back-and-forth on your last ten POs. If the answer is closer to 8 per order than 1 in 8, your team's real job has quietly become transcription — reading supplier emails and re-entering them into whatever tracks the order.

    Both halves of the fix matter: send POs that already contain the answers to the questions suppliers would ask, and absorb the replies you still get into the order itself. That's the workflow LineNow runs.


    Want your POs to answer their own questions? Book a demo to start your 90-day free trial.

    case studymulti-location retailpurchase order automationsupplier communicationsupplier email parsingWhitmans

    Written by Jainul Vaghasia

    Jainul Vaghasia builds LineNow, the purchasing and inventory platform for SMBs. He writes from operator interviews, customer implementations, and the live purchasing workflows LineNow runs for restaurants, retailers, and ecommerce brands.

    Recommended next

    Keep moving through the procurement library.

    Follow the path that matches your funnel stage: definition, operator workflow, buyer evaluation, or product proof.

    View Ecommerce Inventory WorkflowsMap this idea to the closest LineNow product workflow.How LineNow worksWalk through demand signals, purchase orders, supplier replies, receiving, and accounting handoff.Closed-loop procurementUse the core category definition to connect recommendations, POs, supplier replies, and receiving.PricingCheck the trial and plan details when the workflow is a fit.
    Share on X