Replacing a Vertical POS with Shopify Plus: The Procurement Migration Guide
What operators must rebuild when moving from an industry-specific POS to Shopify Plus: supplier POs, central warehouse workflows, receiving, period-based costing, and QuickBooks handoff.Many operators move to Shopify Plus because the old vertical POS cannot keep up with modern commerce.
The old system may have been built for a specific industry: floral, specialty retail, food service, wholesale, rentals, or another niche workflow. It may have handled local pickup, delivery, store orders, inventory shortcuts, supplier habits, and accounting exports in a way that felt dated but familiar.
Shopify Plus is often the right commerce move. It improves storefront, POS, B2B catalogs, checkout, customer accounts, integrations, and operational flexibility.
But replacing a vertical POS creates one hidden project: rebuilding procurement.
The replatforming gap
When a business leaves an older vertical POS, the team usually maps:
- products
- customers
- locations
- taxes
- discounts
- online orders
- POS workflows
- delivery or pickup rules
- accounting sync
Procurement is often treated as secondary until the team asks:
- How do store managers request product?
- Who approves buying?
- How do we create supplier POs?
- Where do supplier replies go?
- How do substitutions update the order?
- Who receives inventory?
- How does the final bill reach QuickBooks?
- What happens to categories where we do not track every unit?
Those questions are not solved by a commerce replatform alone.
Why the old system felt deeper than it was
Vertical POS systems often hide operational depth inside industry-specific assumptions.
A floral system might know about local delivery, wire-outs, pickup dates, arrangements, fresh product, and holiday peaks. A restaurant system might know about ingredients, vendors, menus, and prep. A specialty retail system might know about transfer habits and local supplier relationships.
The system may still be painful. But it has years of workflow sediment inside it.
When Shopify Plus replaces the commerce layer, those hidden workflows have to be rebuilt intentionally. Otherwise the business improves the sales experience while moving procurement back into phone calls, email, spreadsheets, and accounting cleanup.
What Shopify Plus should own
Shopify Plus should usually own:
- online storefront
- Shopify POS
- product catalog
- variants
- B2B catalogs and customer-specific pricing
- checkout
- customer records
- sales orders
- commerce analytics
- basic inventory quantities for selling
That is the sell-side operating system.
What QuickBooks should own
QuickBooks Online should usually own:
- vendor bills
- chart of accounts
- classes or locations
- payments
- bank reconciliation
- financial statements
- accountant workflow
That is the finance system of record.
What the procurement layer should own
The procurement layer should own the buying work between Shopify and QuickBooks:
- supplier records
- supplier SKUs, pack sizes, MOQs, lead times, and costs
- reorder recommendations
- internal store requests
- central warehouse orders
- supplier POs
- supplier replies
- substitutions and price changes
- receiving
- invoice and document capture
- accounting handoff
Without this layer, the operator becomes the integration between Shopify and QuickBooks.
Migration checklist
Use this checklist before turning off the old vertical POS.
1. Identify every buying workflow hidden in the old system
List:
- weekly replenishment
- seasonal or holiday buying
- central warehouse buying
- branch requests
- wholesale orders
- dropship or direct-to-customer supplier orders
- event or special orders
- fresh/perishable purchasing
- hard goods replenishment
Do not assume they all need the same workflow.
2. Split catalog by procurement behavior
A Shopify catalog is not the same thing as a procurement catalog.
Classify items into:
- stocked retail items
- fresh/perishable period-spend items
- recipe/BOM items
- dropship items
- internal warehouse items
- one-off or event items
Each group needs different buying logic.
3. Define location and warehouse rules
For each location, answer:
- Can this location order directly from external suppliers?
- Should this location order only from the central warehouse?
- Which suppliers are approved?
- Who can approve or edit orders?
- Who receives inventory?
- How should spend be allocated?
This is where internal supplier modeling matters. A central warehouse should not be treated as just another stock quantity if it is approving and fulfilling branch orders.
4. Decide accounting treatment before go-live
Before the first production PO, define:
- QuickBooks vendor mapping
- expense, COGS, or inventory accounts
- class/location handling
- bill date and terms
- attachment handling
- invoice mismatch process
- receiving requirement before bill push
Accounting should not discover the new procurement workflow at month-end.
5. Run one complete loop in parallel
Pick one supplier and one category. Run:
- Shopify/POS demand or branch request.
- PO creation.
- Supplier send.
- Supplier reply.
- Receiving.
- QuickBooks handoff.
- Accounting review.
Parallel run beats abstract implementation planning. Real supplier behavior exposes the missing fields and workflow assumptions.
Common mistake: replacing the POS but not the purchasing process
The most common migration failure is assuming that Shopify Plus plus QuickBooks equals operations.
It does not.
Shopify answers: what did we sell?
QuickBooks answers: what did we owe or pay?
Procurement answers: what should we buy, who changed it, what arrived, and what should accounting see?
If nobody owns the third question, the old vertical POS gets replaced by inboxes and spreadsheets.
Common mistake: forcing ERP too early
ERP can solve the gap, but often with more operational weight than the SMB wants.
The buyer may not need:
- full MRP
- HR
- CRM
- enterprise approvals
- formal sourcing
- contract lifecycle management
- months of implementation
They may need:
- branch requests
- supplier POs
- supplier reply tracking
- receiving
- QuickBooks bills
- multi-location visibility
- enough control to stop random supplier calls
That is a procurement workflow layer.
Common mistake: pretending every item needs exact COGS
Some categories should be tracked precisely. Hard goods, packaged products, ingredients with stable recipes, and high-value inventory often deserve item-level cost and margin.
Other categories are better managed as period procurement spend. Highly perishable, variable, or custom inputs may not justify fake precision.
The migration should support both:
- item-level inventory where accuracy matters
- period spend analytics where the operator intentionally treats purchases as COGS
The important part is clean procurement records either way.
The cutover plan
A practical cutover plan looks like this:
- Freeze the old purchasing process for one pilot category.
- Import or sync Shopify products and locations.
- Configure supplier data only for the pilot scope.
- Run one live PO.
- Receive against the latest order state.
- Push or stage the QuickBooks bill.
- Compare against the old process.
- Fix missing fields.
- Add the next supplier/category.
- Turn off old purchasing only after the loop is stable.
The goal is not a perfect catalog on day one. The goal is a working loop that gets cleaner every cycle.
Where LineNow fits
LineNow is designed for operators who want Shopify Plus as commerce and QuickBooks as accounting, but need a serious procurement workflow between them.
It can support:
- supplier-linked item data that Shopify does not model deeply
- POs from inventory, branch demand, manual ordering, or AI-assisted carts
- central warehouse and multi-location buying
- supplier reply tracking
- receiving
- QuickBooks or Xero handoff
- recipe/BOM costing where useful
- period procurement reporting where exact unit COGS is not the goal
If you are replacing a vertical POS, the first question is not "Can Shopify hold the catalog?" It is "What will own the buying loop after the old system is gone?"