A buyer may start an order from a blank form, a stock review, an automated draft, an AI-assisted cart, or a shopping list for a supplier portal. The right starting point depends on the purchase and the way the supplier accepts orders.
This guide helps a buying lead choose how to prepare an order. These five starting points are examples, not an exhaustive product feature list. Customer-order-driven dropship routing is a separate workflow covered in the LineNow ordering guide.
Here are the five ways to build a PO, when each one is right, and what to evaluate for the paths your team uses.
Quick answer
The five practical ways to build a purchase order are: manual entry from scratch, inventory-driven recommendations, automatically staged carts or drafts from reorder triggers, AI-assisted cart building, and off-platform shopping lists for supplier portals or buying trips. A strong procurement system should support more than one starting point, but every path should end in the same operating record: a living PO that can be sent, updated when the supplier replies, received against the current state, and handed to accounting with context.
Choose by what you know at the start
| Starting information | Method to evaluate | Decision before sending |
|---|---|---|
| Exact items and quantities | Manual entry | Supplier terms, destination and purchasing authority |
| Current stock and expected demand | Inventory recommendations | Incoming timing, packs and required quantity |
| A repeatable replenishment policy | Automatically staged cart | Trigger, existing cart coverage and reviewer |
| A business question needing data exploration | AI-assisted cart | Catalog matches, unit basis and supported actions |
| Supplier requires its own checkout | Shopping list | Actual submitted quantity, price and supplier reference |
1. Build it from scratch
The classic. You sit down, pick a supplier, type out the items and quantities, hit send. If all you need today is the document, the free purchase order generator produces a clean PO in the browser. Used when:
- The order is unusual (a one-off — new equipment, a special event)
- The supplier isn't in your regular roster yet
- You're testing a new product before adding it to your standard order guide
What to look for: speed. Time a representative order, including delivery date, payment terms and ship-to review. Speed matters, but a faster form is not useful if it omits the fields needed to resolve a dispute.
2. Build it from inventory recommendations
A useful starting point for stocked replenishment. You open the inventory screen, see which items are below PAR or trending toward stockout, add them to a cart, and the cart becomes a PO. Used when:
- It's your regular order day (Tuesdays, every two weeks, end of week)
- You're reordering items you've ordered many times before
- The system can do the math: how much you've sold, how fast you'll keep selling, what your safety stock should be, what the lead time is from this supplier
What to look for: the recommendation has to actually be right. Test the recommendation on steady, seasonal and intermittent-demand items. A more complex forecasting method is not automatically more accurate; compare its result with the history, stockout periods and known future demand.
When this is the dominant shape, the quality of the recommendations determines whether the buyer trusts the system. Bad recommendations push operators back to memory and spreadsheets.
3. Auto-build a cart or draft for review
Automation can stage recommended items or build a draft when supported conditions are met. Confirm which record is created and who sends it. In LineNow’s inventory workflow, automatic replenishment stages items for purchasing; the operator controls the final send. Useful requirements to evaluate include:
- You have stable, predictable replenishment and want to remove the "build the cart" step entirely
- Your requirement is a scheduled draft, such as Tuesday morning ordering; ask the vendor to demonstrate that trigger rather than infer it from threshold automation
- A specific item crosses a configured threshold and you want it staged for purchasing review
What to look for: trigger flexibility. Different items need different triggers — some are calendar-based, some are threshold-based, some are days-of-stock-based. Confirm which triggers are supported and whether they stage a cart or send a binding supplier request.
A strong version: the system drafts the PO automatically, surfaces it for review, and the buyer clicks send. The buyer reviews the draft instead of rebuilding its lines; additional approvals may still apply.
Dropship routing starts from a customer order and needs its own supplier-allocation, cancellation and fulfillment checks. Passing a stocked-inventory cart test does not establish that routing configuration.
4. AI-assisted (talk to the system about what you need)
With a supported AI cart builder, a request such as "show items below reorder point" can help identify products for a reviewable cart. Test the actual prompt, available data and supported actions; do not assume voice input or every natural-language request is supported. Used when:
- You're under time pressure and need a draft fast
- The order spans multiple criteria (specific supplier, specific stock level, specific category)
- You're new to the system and don't know exactly which screen to click through
What to look for: the model needs to be grounded in your actual data. An AI that hallucinates an item that doesn't exist in your catalog or guesses a quantity is worse than no AI. The right architecture has the model consult your catalog, sales history, and supplier rules — and the operator always reviews the draft before sending.
If the buyer works on a phone, test the cart and review steps on that device before relying on the workflow during a busy shift.
5. Off-platform shopping list
Some purchases are prepared in one place and submitted in another. Some suppliers do not accept email POs — they require you to log into their web store, build the order in their checkout, and submit through their portal. A wholesale web store or buying trip can require this separate checkout step.
For these suppliers, you need a shopping list — the items and quantities you want to order, in the format you can paste or reference when you're on their website. Used when:
- The supplier has a web-only ordering portal
- You want to consolidate items from multiple sources into one weekly shopping run
- You're sending a delivery driver out and need a paper list
What to look for: build the list from reviewed stock and demand inputs, then record the actual checkout and supplier reference. Confirm whether confirmation capture is supported or manual. A shopping list is not proof that the supplier accepted an order; avoid sending a duplicate PO after portal checkout.
Worked example: the list and the checkout disagree
A buyer prepares a shopping list for four cases of twelve bottles at an expected $30 per case: 48 bottles and $120. At the supplier portal, only three cases are available at $32 per case. If the buyer accepts, the actual submitted order is 36 bottles for $96 before tax and freight. Keep the original need and the portal confirmation together.
The $24 reduction in order total is not a saving on the same basket. The three cases cost $6 more than their original $90 estimate, and one case was not purchased. Decide whether the remaining twelve bottles are still needed before opening another order. A saved shopping list does not establish an outstanding supplier commitment for them.
If 34 bottles physically arrive against the confirmed 36, record 34 received and resolve the two-bottle short. Never record the original 48 as received merely because that was the list quantity. This fictional example tests commitment and receiving records without assuming a portal connector is available.
Combine only the methods your team needs
Operators often end up with a half-broken procurement workflow because they picked a tool optimized for one of these five shapes. Email-PO-only tools may not handle web-portal suppliers. Recommendation-only tools may not help with one-off orders. Manual-only tools can become slow as supplier count grows.
Some teams use several paths in the same week. The Tuesday produce order is from inventory. The Friday equipment-repair part is built from scratch. A bar’s staple items are staged when configured thresholds are met. The "what should I order from Charlie's?" question on a phone uses AI. The Restaurant Depot run uses a shopping list.
In LineNow, evaluate the paths your team needs and how each reaches a traceable purchase record. Replies from supported supplier channels become updates for review; physical receipts and accounting handoff use their configured processes. This is the closed-loop procurement approach: keep the order, changes, and receipt together.
A diagnostic for your current setup
Three questions:
- Of the five shapes above, how many does your current system support? List only the paths your team uses.
- When you need a shape your system doesn't support, where do you go? Spreadsheets? Email? A different tool?
- How many tools and tabs are open during a normal procurement morning?
Record the time spent on the handoffs that matter. Two well-supported paths may be enough for your team; a longer feature list is not a reason to add setup work.
The fix
Choose the paths that remove repeated work while preserving the supplier commitment, review decision and receipt. Different starting points need not use the same forecasting method or integration. Review the LineNow workflow guide for the distinction between automatic cart staging and configured dropship forwarding, and confirm required features in current pricing.
Bring one regular replenishment order and one exception to a demonstration. Start with retail inventory replenishment if deciding what to buy is the bottleneck, or PO status tracking if supplier changes and follow-up consume the time.