PalletLoop replaces the email chains, spreadsheets, and phone calls between your team and your 3PLs with a single live platform — for every pickup, rejection, and transit return. Your warehouse closes the loop. You see it happen.


Once a pallet leaves a customer location or gets rejected at delivery, it disappears into a fog of emails, spreadsheets, and phone calls. By the time it reaches the warehouse — if it does — quantities are disputed, credit notes are delayed, and nobody can prove what happened.
Returns reconciled days or weeks late mean shrinkage you can't prove and credit notes you can't defend.
Customer service, warehouses, and transporters all work from different data. Discrepancies surface too late to act on.
When something goes wrong, you can't see who actioned what, when, or why. Disputes turn into stand-offs.
Two scenarios, four roles, one source of truth. Set up in days, not months.
Customer service creates a pickup return, or a transporter logs a rejection at delivery. Pallets, cases, SKUs, ETA — all captured in seconds against your existing master data.
The right partner — warehouse, transporter, or both — is alerted in-app and by email. No more chasing or copying inboxes.
Every stakeholder sees the same status, in real time. Status changes are timestamped, audit-logged, and visible on role-specific dashboards.
The warehouse confirms actual quantities against expected, runs your quality checklist, and routes any discrepancies to your nominated reviewers for a scrap-or-restock decision.
Role-based access scoped down to the right warehouse, the right transporter, the right team. Enforced at the database layer — not just the UI.
Configure master data, quality checklists, aging thresholds, and discrepancy workflows. See every warehouse, transporter, and customer.
Create pickup return requests with full consignment detail. Track status without picking up the phone.
Receipt workflow, quality checks, and disposition actions in one place — scoped to your warehouses, nothing else.
See only the returns assigned to your org. Log delivery rejections from the field with the delivery reference.
Not a generic returns tool. Every workflow shaped by the way operators, warehouses, and transporters actually move stock.
Customer pickups, delivery rejections, and en-route disposals — all handled in the same lifecycle, with scenario-specific fields and workflows.
One checklist per SKU category. Warehouse teams run through it at receipt — pass, fail, or notes. Versioned so audits stay clean.
When actual doesn't match expected, the return automatically routes to your nominated reviewer for a scrap-or-restock decision.
Configure aging thresholds for each status. Stuck returns surface on dashboards and trigger email alerts before they become problems.
Warehouses, transporters, customers, SKUs — managed by you, uploaded by CSV in bulk, used everywhere.
Return volumes, aging, scrap rates, top discrepancy reasons. Export to CSV. No spreadsheet exports from your 3PL ever again.
Transporter isolates damaged stock in transit. Parent admin approves disposal or routes back to warehouse. Photo evidence uploaded and logged.
Toggle optional statuses per scenario to match how your network operates. The state machine adapts at runtime — no development work required.
Every status change, quantity edit, and disposition decision recorded with actor and timestamp. Exportable for finance reconciliation and dispute resolution.
PalletLoop is built on infrastructure trusted by tens of thousands of businesses. Your data — and your partners' data — is isolated at the database layer, encrypted at rest and in transit.
“We used to spend hours every Monday reconciling returns across three 3PLs. With PalletLoop, it happens in real time. We've cut our average reconciliation time from days to hours.”
No. PalletLoop sits alongside your existing systems and focuses on the returns blind spot they don't cover. Webhook and API integrations are on the roadmap so PalletLoop can push reconciled data wherever you need it.
Most teams are live and setup within hours. Master data setup (warehouses, transporters, SKUs, customers) can be uploaded by CSV. We help you bring your 3PL partners on board.
That's exactly what PalletLoop is built for. Each partner sees only their own scope, parent admin sees the whole network.
No. PalletLoop is paid for by the FMCG parent company. 3PL partners are invited at no cost — they get a better tool, you get visibility.
The warehouse runs your configured quality checklist at receipt. Discrepancies (quantity or quality) automatically route to your nominated reviewer, who decides whether the stock is scrapped or returned to inventory. That decision is logged and actioned by the warehouse team.
You configure master data, quality checklists per SKU category, aging thresholds per status, and discrepancy reviewers. The core lifecycle is standardised so your 3PL partners have one way of working with you.
Yes. Data is isolated at the database layer using row-level security policies, not just at the UI. Your 3PL partners only see your data — and only the parts they're scoped to.
PalletLoop handles this with en-route disposal returns. The transporter isolates the damaged stock and logs it in the platform with a reason code. A parent admin then decides: approve disposal (the transporter uploads photo evidence and confirms) or route it back to the warehouse for assessment. Every decision is recorded and auditable.
Yes. PalletLoop is built for Australian operators and complies with the Privacy Act 1988 and the Australian Privacy Principles (APPs). Your data is hosted in AWS ap-southeast-2 (Sydney) and never leaves Australia. We act as a data processor — you own your data and can request deletion at any time. See our Privacy Policy for full details.
Your 3PL partners — warehouses and transporters — get full access at no cost. They get a better tool. You get visibility across your entire network. No setup fees.
What's included
Everything in Starter, plus
A 20-minute demo is enough to see whether PalletLoop fits your operation. No prep needed — just bring one returns scenario you'd like to walk through.