How do I set up an order management system for reserve in store and buy online pickup across multiple locations?

Setting up an order management system for Reserve in Store and Buy Online, Pick Up in Store (BOPIS) across multiple locations usually comes down to 5 things:

1. Inventory visibility
2. Store fulfillment rules
3. Order routing
4. Pickup workflow
5. Systems integration and reporting

Here’s a practical blueprint.

---

1) Define the order types and workflows

You’ll usually want separate but related flows:

Reserve in Store

Customer:

• Browses online
• Selects a store
• Reserves item for a limited time
• Pays later in store, or completes purchase after pickup

Typical requirements:

• Soft hold inventory for a time window
• No payment capture, or sometimes a deposit
• Automatic release if not collected

Buy Online, Pickup in Store

Customer:

• Places and pays online
• Order is routed to a store with available stock
• Store picks/ages the order
• Customer receives ready-for-pickup notification
• Pickup is confirmed at collection

Typical requirements:

• Real-time or near-real-time inventory
• Payment authorization/capture rules
• Store picking status and handoff confirmation

---

2) Build a centralized inventory model

This is the foundation.

You need inventory by:

• Location
• SKU
• Sellable quantity
• Reserved quantity
• On-hand quantity
• Safety stock / buffer
• Inbound stock

Example:

• On hand: 20
• Safety stock: 2
• Reserved: 5
• Sellable: 13

Important rules:

• Never promise “on hand” inventory directly to customers
• Show only available-to-promise stock
• Deduct stock only when the order is accepted/confirmed
• Use reservation timers to prevent overselling

Best practice:

Use a single inventory service as the source of truth, even if stores have POS systems or local stock files.

---

3) Establish store eligibility and routing logic

Not every store should fulfill every order.

Store qualification rules may include:

• Inventory availability
• Distance from customer
• Store hours
• Pickup capability
• Staffing capacity
• Product category restrictions
• Same-day cutoff times
• Blackout dates

Routing options:

• Customer-selected store: customer chooses from eligible stores
• System-selected store: OMS selects best store automatically
• Hybrid: show recommended store, allow override

Routing logic example:

1. Check item availability
2. Filter stores by pickup eligibility
3. Apply cutoff time and fulfillment SLA
4. Prefer closest store with enough inventory
5. Send order to best store

---

4) Define reservation and order lifecycle states

You need consistent statuses across all locations.

Reserve in Store statuses:

• Available
• Reserved
• Reservation Expired
• Converted to Sale
• Cancelled

BOPIS statuses:

• Created
• Payment Authorized
• Routed to Store
• Accepted by Store
• Picking
• Ready for Pickup
• Picked Up
• Cancelled
• Expired / Unclaimed
• Refunded / Voided

Store-side statuses:

• Pending assignment
• Acknowledged
• In progress
• Complete
• Exception / out of stock

This makes it easier to integrate OMS, POS, warehouse, CRM, and notification systems.

---

5) Set service-level agreements and timers

These are critical for customer experience.

Common timers:

• Reservation hold: 15 min, 1 hour, or same-day pickup window
• Pickup ready SLA: 1–4 hours or next day
• Pickup expiration: 2–7 days
• Store acceptance SLA: 5–30 minutes
• Picking SLA: same day or within a set window

You should automate:

• Hold expiration and release of inventory
• Reminder notifications
• Escalation if store doesn’t acknowledge
• Auto-cancel after pickup expiry

---

6) Integrate the right systems

A multi-location OMS usually connects these systems:

Core systems

• Ecommerce platform: order capture, product catalog
• OMS: orchestration and routing
• POS: in-store pickup verification, final sale if needed
• Inventory management: stock availability
• WMS: if you have backroom/warehouse fulfillment
• CRM / CDP: customer notifications and history
• Notification service: email/SMS/app alerts

Common integrations:

• Real-time inventory sync from POS to OMS
• Order injection from ecommerce to OMS
• Store pickup confirmation back to OMS and ecommerce
• Refund/void updates back to payment gateway

Preferred architecture:

• Event-driven if possible
• API-based integrations with webhooks
• Retry and reconciliation jobs for failed syncs

---

7) Design the store operations workflow

Store execution is where many programs fail.

Store process for BOPIS:

1. Order assigned to store
2. Staff receives task queue
3. Staff picks item(s)
4. Staff scans item and verifies SKU
5. Store marks order ready
6. Customer gets notification
7. At pickup, staff confirms identity/order number
8. POS or OMS marks order collected

For reserve in store:

1. Store sees reserve request
2. Inventory is held
3. Customer is notified with pickup/reservation details
4. Store confirms when customer arrives
5. If customer buys, POS completes transaction
6. If not, reservation expires and inventory returns to available

Operational best practices:

• Dedicated pickup area
• Barcode scanning for verification
• Exception handling for partial fills
• SOPs for substitutions, damages, and lost orders

---

8) Handle exceptions and edge cases

Plan these early.

Common exceptions:

• Item out of stock at assigned store
• Customer wants a different pickup store
• Reservation expires before pickup
• Partial order fulfillment
• Damaged item found during pick
• Duplicate orders
• Payment failure or fraud review
• Store closes before pickup

Policies to define:

• Can you split items across stores?
• Can customers substitute sizes/colors?
• Can store transfer stock from another location?
• When do you refund automatically?
• What happens if a customer no-shows?

---

9) Define customer communication rules

A good experience depends on clear notifications.

Notifications to send:

• Reservation confirmed
• Order confirmed
• Store assigned
• Ready for pickup
• Pickup reminder
• Reservation expiring soon
• Order cancelled / expired
• Refund issued

Channels:

• Email
• SMS
• App push
• Order status page

Make sure messages include:

• Store address
• Pickup hours
• Pickup deadline
• Order number
• ID requirements

---

10) Set metrics and reporting

You’ll want to monitor performance by store, SKU, and channel.

Key KPIs:

• Reservation conversion rate
• BOPIS order fill rate
• Pick time
• Ready-for-pickup SLA compliance
• Inventory accuracy
• Cancellation rate
• No-show rate
• Customer wait time
• Store acceptance time
• Refund/exception rate

Useful dashboards:

• By store
• By region
• By product category
• By hour/day
• By channel

---

11) Choose your implementation approach

Option A: Use an off-the-shelf OMS

Best if you need speed. Look for:

• Multi-location inventory
• Store routing
• Reservation holds
• Store task management
• POS integration
• Notifications
• Order state tracking

Option B: Build on top of existing commerce platforms

Best if you already use a strong ecommerce stack. You’ll need:

• Inventory service
• Rules engine
• Store app or portal
• Webhooks/API orchestration

Option C: Custom build

Best for complex rules, but more expensive. Use:

• OMS core
• Inventory microservice
• Store fulfillment app
• Event bus
• Integration layer

---

12) Recommended architecture pattern

A common pattern:

• Ecommerce storefront → checks availability with OMS/inventory
• OMS → reserves inventory → routes order to store → manages status
• Store app/POS → picks and confirms order
• Notification service → sends customer updates
• Inventory service → updates sellable stock in real time

Use:

• APIs for synchronous requests
• Events for state changes
• Scheduled reconciliation to catch discrepancies

---

13) Rollout plan

Start small.

Phase 1: Pilot

• 1 region
• 3–5 stores
• 100–200 SKUs
• Simple pickup workflow

Phase 2: Expand

• Add more stores
• Add routing optimization
• Add reserve in store
• Add escalation and exception handling

Phase 3: Optimize

• Forecast demand
• Improve inventory accuracy
• Add staffing recommendations
• Automate substitutions or transfers

---

14) Simple process flow example

BOPIS example

1. Customer orders online
2. OMS checks availability across stores
3. Best store is assigned
4. Inventory is reserved
5. Store receives pick task
6. Staff picks and confirms item
7. Customer gets “Ready for pickup”
8. Customer arrives and collects order
9. OMS closes order and updates inventory

Reserve in Store example

1. Customer selects store and reserves item
2. OMS creates time-limited hold
3. Store receives reservation record
4. Item is held from available stock
5. Customer picks up and pays in store
6. Sale is completed in POS
7. Reservation closes

---

15) Questions you should answer before implementation

• Do customers choose the store, or does the system choose?
• How long should reservations last?
• Can a store reject an order?
• How often does inventory sync?
• Can orders be split across stores?
• Will payment be captured immediately or at pickup?
• What’s the fallback if the picked item is damaged?
• How will store associates work the queue?
• What’s the pickup expiry policy?

---

If you want, I can also give you:

1. a sample OMS architecture diagram,
2. a detailed workflow for store staff, or
3. a requirements checklist for vendors/software.