Skip to main content
Talk to an expert
Peoplevox logo

Peoplevox integration for ecommerce fulfilment

Orders flow reliably from commerce into the warehouse clean iWeb connects your commerce platform, OMS and ERP with Peoplevox so orders move into dispatch without loss, tracking reaches customers on time, stock stays reconciled, and exceptions are visible before they become escalations. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: shipping connector, warehouse integration, fulfilment plugin, app.

PeoplevoxiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Peoplevox integration gives you.

Orders move reliably from order queue into the warehouse

Dispatch instructions reach Peoplevox with complete customer, line item and address data. Picking starts on time and order status is visible to both the warehouse and the storefront.

Customers see tracking and despatch confirmations on time

Dispatch events and carrier tracking flow back to commerce so order status pages and customer emails update automatically. No manual shipping-notification work, and no missed shipments.

Stock records stay current in your ERP and storefront

Each warehouse movement—pick, pack, adjust, transfer—flows back to the ERP so the stock ledger and inventory availability reflect what is physically in the warehouse.

Returns and credits process without delays or gaps

Return items flow back through Peoplevox to the restock or disposal process, and credit notes are issued in step with physical goods receipt. No orphaned returns or stuck refund requests.

Warehouse exceptions are visible and owned

Unshipped orders, label failures, carrier rejections and stock discrepancies surface in monitoring dashboards. Operations teams respond quickly instead of discovering issues days later during reconciliation.

02 · When it's worth it

Where a Peoplevox integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Move orders from commerce platforms and OMS systems into Peoplevox for picking, packing and dispatch
Return dispatch confirmations, tracking numbers and label data back to commerce and customer communications
Sync stock movements and adjustments between Peoplevox and your ERP for ledger accuracy
Route returns and RMA events between Peoplevox, commerce and the ERP credit process
Surface unshipped orders and warehouse exceptions so they do not queue silently
Reconcile physical despatch against orders and invoices for revenue recognition
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

No native order-status polling

Peoplevox does not automatically push real-time order status back to commerce platforms. You must pull status via API queries or set up webhooks to keep the storefront current on unshipped orders.

Limited multi-location orchestration

Peoplevox handles warehouse operations well but does not automatically route orders across multiple fulfillment locations. You need an OMS or orchestration layer to decide which warehouse picks each order.

ERP stock reconciliation requires manual mapping

Stock movements in Peoplevox do not automatically reconcile against your ERP ledger. You must define which Peoplevox adjustments map to which ERP nominal codes and cost centres.

Return workflows need business-rule configuration

Peoplevox receives returns but does not automatically decide whether to restock, scrap or send for inspection. You must configure return disposition rules and link them to your credit and stock processes.

Label and carrier integration is carrier-specific

Peoplevox supports multiple carriers but label formats, rate shopping and tracking handoff vary. Your integration must account for carrier-specific field mapping and exception handling.

04 · The real work

Most dispatch delays surface weeks later in customer service or reconciliation, not because the warehouse is slow but because order status never flowed back from the warehouse to the storefront.

05 · Where it sits

Where this integration sits in your estate.

Peoplevox holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Commerce platform agnostic. Connect Peoplevox across your entire technology stack.

System of record
Source / owner
Peoplevox
Cloud warehouse management and dispatch orchestration
  • Picking and packing workflows
  • Despatch instructions and confirmations
  • Carrier label generation and tracking data
  • Returns goods receipt and disposition
  • Stock movement recording
  • Warehouse exception queues
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Customer order creation and confirmation
  • Order status display and customer comms
  • Return / RMA initiation
  • Stock availability for catalogue display
  • Checkout and cart management
Connected neighbours
Integration layer
ERP
Owns stock ledger and financial posting; receives movements from Peoplevox; owns credit process for returns.
Integration layer
OMS / routing layer
Owns order-to-location routing; passes complete instructions to Peoplevox; consumes despatch and tracking events.
Integration layer
Carrier networks
Rate, label and tracking provider; receives labels from Peoplevox; returns tracking events back to the platform.
Integration layer
Customer comms
Email, SMS and account-centre notifications; consumes despatch and tracking from Peoplevox; sends returns notices to customers.
Integration layer
Marketplace channels
Order sources alongside native ecommerce; orders flow to Peoplevox; tracking and returns flow back to each channel.
Integration layer
Reporting and BI
Consumes dispatch, stock movement and returns data from Peoplevox for operational dashboards and forecasting.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, NetSuite, Sage 200)
  • Order Management System (OMS)
  • Commerce platform
  • Marketplace connectors (Amazon, eBay, Etsy)
  • Carrier management system
  • Customer comms (email, SMS)
  • Business intelligence / reporting
  • Accounting system
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE & ERP
←From COMMERCE
↔BOTH WAYS
Orders into fulfilment: Confirmed orders from your ecommerce platform or OMS flow to Peoplevox with customer, line item and delivery details
The warehouse system receives picking instructions and triggers the despatch process.
Dispatch and tracking events: Once orders ship, Peoplevox sends back despatch confirmations, carrier tracking numbers and label references
These data reach the storefront so customers see status updates and tracking links.
Stock movements and adjustments: When stock is picked, packed or adjusted in the warehouse, Peoplevox records the movement
This data flows to your ERP so the stock ledger stays current and financial records reflect actual physical inventory.
Returns and RMA handling: Returns initiated in commerce or through a customer service system flow to Peoplevox for goods-receipt and restocking
Completed return events feed back to commerce and the ERP credit note process.
Inventory top-ups and transfers: Stock transfers between locations or top-ups triggered in commerce or your ERP reach Peoplevox so warehouse operations match planned inventory moves.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Order-intake design

    We define how orders hand off from commerce or OMS to Peoplevox—which fields are required, how addresses are normalised, what happens if Peoplevox is temporarily unavailable. Orders reach the warehouse queue with no data loss or duplication.

  2. 02
    Dispatch and tracking orchestration

    We configure how despatch confirmations, tracking numbers and labels flow back to commerce, customer email and order-management systems. Status pages update automatically and no shipping-related manual work backs up.

  3. 03
    Stock-movement mapping

    We map Peoplevox adjustments to your ERP nominal codes, cost centres and stock ledger locations. Reconciliation is clean and month-end close does not expose stock discrepancies.

  4. 04
    Returns and exception handling

    We build return workflows so goods come back through Peoplevox, trigger the right credit and restock processes, and communicate with the customer. RMA events reach both commerce and finance systems in the right sequence.

  5. 05
    Monitoring and alerting

    We set up observability so unshipped orders, carrier failures, label errors and stock anomalies trigger alerts. Operations teams know about issues in minutes, not days.

  6. 06
    Fallback and resilience

    We define how commerce platforms handle Peoplevox outages—whether orders queue locally, hold in a buffer, or stop checkout gracefully. Downtime does not create orphaned orders or lost transactions.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataDispatch instructions and order acknowledgement
Source / ownerCommerce platform / OMS
Maintained byPeoplevox confirms receipt and triggers picking
NotesCommerce or OMS owns the customer order; Peoplevox acknowledges and schedules despatch.
DataStock adjustments and warehouse movements
Source / ownerERP
Maintained byPeoplevox records the physical movement; ERP ledger is updated via integration
NotesPeoplevox is authoritative for physical warehouse state; ERP is the ledger of record for financial stock value.
DataDespatch confirmations and carrier tracking
Source / ownerPeoplevox
Maintained byPeoplevox generates; commerce and customer comms consume
NotesPeoplevox creates the dispatch event and tracking link; this data flows to commerce platforms and customer notifications.
DataReturns and RMA disposition
Source / ownerPeoplevox
Maintained byPeoplevox records goods receipt; ERP and commerce consume disposition and credit events
NotesPeoplevox decides restocking, disposal or inspection; credit process and stock recount follow the disposition decision.
DataLabel and carrier data
Source / ownerPeoplevox
Maintained byPeoplevox manages carrier rates, label formats and tracking feeds
NotesPeoplevox integrates with carriers; commerce and fulfillment depend on clean label and tracking output.
DataUnshipped and exception queues
Source / ownerPeoplevox
Maintained byIntegration monitoring and operations teams
NotesPeoplevox holds unshipped orders; integration monitoring surfaces them so operations can triage.
10 · Experienced integrator

Built this integration before

iWeb has designed and operated Peoplevox integrations across ecommerce estates with multi-channel order routing, multi-location fulfillment and complex return workflows. We understand how Peoplevox sits between order intake, warehouse operations, ERP stock ledgers and customer expectations.

We design order-intake flows so Peoplevox receives validated data and commerce platforms do not block on warehouse unavailability.
We map despatch events and carrier tracking back to commerce and customer systems so status updates are automatic and accurate.
We own stock-movement reconciliation so your ERP ledger stays current and month-end does not expose discrepancies.
We build returns and exception handling so RMA events reach finance, operations and customers in the right sequence.
We configure monitoring and alerting so unshipped orders, label failures and warehouse exceptions surface before they affect customer experience.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Validate that test orders move from commerce into Peoplevox and generate picking instructions without delays or data loss.
Confirm that despatch confirmations and tracking numbers flow back to the commerce platform and appear in order-status pages within seconds of Peoplevox confirmation.
Test that stock movements (pick, pack, adjust) are recorded in Peoplevox and posted to the ERP ledger with correct nominal codes.
Verify that returns flow into Peoplevox, trigger the right disposition, and generate credit notes in the ERP in the correct sequence.
Confirm that unshipped orders and carrier label failures surface in monitoring dashboards and trigger alerts before customers escalate.
Test fallback behaviour—place an order while Peoplevox is unreachable and confirm it either queues or holds gracefully without breaking the storefront.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Orders stuck in commerce queues

If the Peoplevox integration fails silently, orders may sit in your commerce platform waiting for acknowledgement while customers expect shipment. Unmonitored queues create delays that surface only when customers complain.

Tracking information never reaches the customer

If despatch events or tracking numbers do not flow back from Peoplevox, order status pages stay blank and customer emails omit tracking links. Support teams field enquiries about shipments already on the way.

Stock ledger drifts from physical warehouse counts

If stock movements in Peoplevox are not reliably mapped back to the ERP, the ledger diverges from reality. Month-end reconciliation uncovers lost adjustments or unrecorded damage / shrinkage.

Returns get lost between the warehouse and credit process

If return items flow into Peoplevox but disposition rules are unclear, goods sit in a holding area while the credit system has already issued a refund. Stock and finance records become misaligned.

Carrier rule changes break label generation silently

When a carrier updates field requirements or weight handling, Peoplevox labels may fail validation without warning. Unshipped orders accumulate until someone manually tests the label feed.

Multi-location order routing creates oversell

Without an orchestration layer, orders can be claimed by multiple warehouses or get stuck because no location has stock reserved. Peoplevox processes the order twice or the despatch hangs indefinitely.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Peoplevox integrations.

How do orders flow from our ecommerce platform into Peoplevox?

Orders confirmed in your commerce platform are sent to Peoplevox via API with customer, line-item, address and delivery details. Peoplevox acknowledges receipt and queues the order for picking. If Peoplevox is temporarily unavailable, orders can queue in a buffer or hold in commerce until the connection recovers.

How does the customer know when their order has shipped?

Once Peoplevox generates a despatch confirmation, it sends back the carrier name, tracking number and label reference. This data flows to your commerce platform so the order status updates automatically and the customer receives an email with a tracking link.

What happens if Peoplevox is down—does it break checkout?

No. We design the integration so that brief Peoplevox outages do not block the storefront. Orders can queue locally in commerce or in a buffer system, and resume flowing to Peoplevox once the connection is restored. Longer outages are surfaced by monitoring so operations can decide next steps.

How do stock movements in Peoplevox get back to our ERP?

Each time stock is picked, packed or adjusted in the warehouse, Peoplevox records the movement. This data flows to your ERP where it updates the stock ledger and cost centre postings. We map each movement type to the right ERP nominal code so reconciliation stays clean.

How are returns handled when a customer sends goods back?

Returns flow into Peoplevox where they are registered as inbound goods. Peoplevox applies disposition rules—restock, inspection, scrap or return to supplier. Once disposition is complete, the data flows to your ERP credit process and your commerce platform so the refund and stock recount happen in the right sequence.

Can Peoplevox split a single order across multiple warehouse locations?

Peoplevox can handle split picking if an OMS or orchestration layer pre-assigns lines to specific locations. Peoplevox does not automatically route; an upstream system must decide which location picks which lines.

How do we know if orders are stuck in the warehouse queue?

We set up monitoring so unshipped orders, carrier label failures and despatch delays trigger alerts. Operations teams see these exceptions in real time and can investigate or escalate before customers follow up.

What happens if a carrier rejects a label or tracking fails?

Peoplevox surfaces carrier rejection errors. We build alerts so you know immediately when a label fails validation. Most failures are temporary (address format, weight mismatch) and can be corrected and resubmitted quickly.

How do we handle click-and-collect or in-store pickup orders in Peoplevox?

Click-and-collect orders can flow to Peoplevox for picking and customer notification. Alternatively, they can bypass Peoplevox if your branch system handles local pickup directly. The integration design reflects your fulfillment model.

Can Peoplevox integration work with multiple ecommerce platforms or marketplaces?

Yes. Orders from multiple storefronts and marketplace channels can all flow to Peoplevox through a single integration layer. We handle channel-specific formatting and ensure despatch and tracking flow back to each source correctly.

How do we reconcile Peoplevox stock movements with our month-end close?

Each stock movement is mapped to an ERP nominal code and cost centre. At month-end, the integration history is auditable so finance teams can reconcile warehouse adjustments against the stock ledger.

What if we upgrade Peoplevox or change warehouse locations?

We design the integration to be location and version agnostic. Changes to Peoplevox configuration (new warehouse, new carrier, software update) are absorbed into the integration without rework, as long as the core API contracts remain stable.

Can we test the integration without affecting live orders?

Yes. We recommend a sandbox environment so you can validate order flows, despatch, returns and stock movements before they touch real inventory or customers. Once you are confident, you can gradually shift traffic to the live integration.

How do we handle exceptions like damaged goods or address validation failures?

Exceptions surface in monitoring dashboards. Operations teams can correct data in Peoplevox (update address, mark as damaged) and resubmit. The integration tracks which orders need manual attention so nothing is forgotten.

Next step

Have a Peoplevox integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →