Skip to content
CLAIM CORE
For 3PLs For brands Integrations Pricing Docs Changelog
Sign in Book a demo Start free

CLAIMS FOR 3PLs AND THE BRANDS THEY SHIP FOR

A claim opens. Claim Core closes it.

Claims arrive from the brands you ship for and from their shoppers. Claim Core pulls the despatch record out of your warehouse system the moment one is raised, puts three clocks on the answer, and keeps the decision somewhere nobody can quietly revise it.

Start on the free plan Book a demo
  • 25 claims a month, free, no card
  • Helm installs from its own app store
  • Built in the UK
Illustrative interface. A claims queue across every brand, 142 open and three breaching, with one claim under review and four hours twelve minutes left on its decision, one with the brand and its clock paused, one accepted in three hours, one breached, and one closed by an automation rule. Beside it the evidence on that claim: a forty-one second pack-station video from camera six on Helm, the despatch time, the packer and the courier. Built from Claim Core's own statuses, SLA clocks and claim types. Not a screenshot of a live account, and the brands named are invented.

THE SHAPE OF A CLAIM

Open on one side. Closed on the other.

Our mark is an arc that has not met itself yet. That is a claim: something a brand or a shopper has opened and is waiting on you to close. Five moves close it, and Claim Core owns all five.

5 moves one record, start to finish
  1. 01

    It is raised, and matched

    From your own desk, from a brand's portal, or from a shopper on a claims page carrying the brand's name. Claim Core matches it to the despatched order as it is created.

  2. 02

    The warehouse record is attached

    At creation, not when somebody remembers to go and look. Where Claim Core cannot establish which brand an order belongs to, it declines to search rather than guessing.

  3. 03

    Somebody reviews it, on a clock

    Assign it, read the evidence, ask the brand for what is missing. The decision clock pauses for exactly as long as the brand owes you a reply.

  4. 04

    It is decided, with what was granted

    Accepted or rejected, and on an acceptance the record says what was given: a refund with an amount, a replacement, something else, or nothing at all.

  5. 05

    It closes, and stays closed

    The shopper hears from the brand, in the brand's name and from the brand's address. If you want the item back, a return opens. The trail cannot be edited afterwards.

3

clocks on every claim

First response, decision, and the reply the brand owes you. The decision clock stops while you are waiting on them and starts again when they answer.

6

warehouse systems, one claim page

Helm is generally available. ShipHero, Mintsoft, Clarus, Deposco and Linnworks are in beta. A field one of them cannot supply says so by name.

0

rows of the trail you can edit

Audit events refuse to be updated or deleted, one at a time or in bulk, and an administrator acting as somebody else is recorded as themselves.

WHO IT IS FOR

Two sides of every claim. One record.

The 3PL buys Claim Core and decides the claims. The brands it ships for work in a portal in their own name, and pay nothing. A brand that runs its own warehouse runs both sides itself.

IF YOU ARE THE 3PL

You decide the claims. This is your desk.

One queue across every brand you ship for, with filters for what is assigned to you, what nobody has picked up and what breaches today.

  • Routing you choose. Shopper claims come straight to you, or go to the brand first and reach you only when they need the warehouse.
  • Rules for the routine. Deterministic if-then rules assign, route and auto-approve. A rule that cannot be certain steps aside and writes down why.
  • Self-service limits. The claim window, claims per order, a value cap and what a shopper may ask for. Set once, overridden per brand.
  • Reports and exports by brand, claim type and outcome, for the conversation you have every quarter.
How it works for 3PLs

IF YOU ARE THE BRAND

Raise it, follow it, settle it, in your own name.

A portal in the brand's colours rather than the warehouse's, and a claims page your shoppers reach without an account.

  • No email chain. Raise a claim against an order, see where it has got to, and read the warehouse record the 3PL read.
  • Decide first, where your 3PL allows it, and pass a claim to them with a reason when you need the warehouse to answer.
  • Your shopper hears from you. The outcome email goes out in your name, from your address, never from ours.
  • Nothing to pay when your 3PL runs Claim Core. Run your own warehouse and you buy a plan like anyone else.
How it works for brands
What differs between a 3PL and a brand
What differs For 3PLs For brands
Who you areThe warehouse that ships for other peopleThe brand whose name is on the parcel
Where you workThe claims desk, across every brandA portal in your own colours
What you decideEvery claim, unless you route it to the brand firstShopper claims, where your 3PL routes them to you
What you setSLAs, routing, automation and self-service limitsYour colours, your claims address, your team
How you startSign up and connect your warehouse systemAsk your 3PL to invite you, or sign up if you fulfil in-house
What it costsA plan, from freeNothing, through your 3PL

EVIDENCE

The proof was in the building the whole time.

Your warehouse already recorded what happened. Claim Core's job is to have it on the claim before anyone argues about it.

What arrives with the claim

  • The despatch: when it left, the warehouse order it left under, and its status.
  • The courier and the tracking, with the delivery status the warehouse system reports.
  • The people: who picked it, who packed it, who despatched it.
  • Serials and lots where the warehouse tracks units, so the claim is about one specific item.
  • Pack-station video on Helm. The warehouse's own links expire, so Claim Core copies the clip into its own storage the first time anyone watches it and keeps it for 90 days after the decision.

And what it says when it cannot

Six warehouse systems do not expose the same things. A claim page that goes blank where a field is missing teaches your team to distrust all of it, so Claim Core does the opposite.

  • “Not supported by Mintsoft” means that system cannot give us this. “N/A” means it could and this order has none. The two never look the same.
  • Uploads are read by their bytes, not their file name, and both the stored extension and the served type are rewritten to match.
  • A shopper's claim is matched or refused, not guessed at. Where the brand behind an order cannot be established, Claim Core does not search.
  • Share it with the brand section by section, so they see the evidence the decision rested on rather than a verdict.

INTEGRATIONS

Live in an afternoon.

Helm installs from its own app store with nothing to copy and nothing to paste. The rest connect with a key or an install link.

  • Helm LIVE
  • ShipHero BETA
  • Mintsoft BETA
  • Clarus BETA
  • Deposco BETA
  • Linnworks BETA
  • Brightpearl SOON
  • Base WMS SOON

Beta means built and tested against that system's published API and not yet running for a customer in production, so we connect the first customers on each one ourselves. The badge comes off as soon as a customer is live, not when it suits us. See what each system supplies.

TRUST

What we will claim, and what we will not.

We have no customer logos on this page and no statistics, because we have not earned the first and you cannot check the second. Here is what the code actually does.

Tenants fail closed, not open

Every tenant-scoped query is filtered to the current organisation by the data layer rather than by the view that happens to remember. A query that loses its scope returns nothing.

The trail refuses to change

Saving an existing audit row raises. Deleting one raises. Bulk updates and bulk deletes raise. The foreign keys are set so that deleting something else cannot route around it.

Automation will not guess

A claim with no priced lines satisfies no value condition at all, including “equals zero”, so a rule that approves anything under £10 cannot quietly approve everything unpriced.

We hold neither ISO 27001 nor SOC 2

No single sign-on, no SAML and no two-factor authentication yet either. We would rather be straight with you than imply something we do not have. Read the security page.

PRICING

The 3PL pays. The brands do not.

Plans are bought by the organisation that decides the claims. Every brand it ships for gets a portal inside that plan.

Starter

Free

One brand, 25 claims a month, the whole claim workflow. Permanently free, with no card. That is the trial.

Start on the free plan

Professional FIRST PLAN WITH A WAREHOUSE INTEGRATION

£149 a month

Up to 10 brands, 500 claims a month, one warehouse integration and 10 automation rules.

Start free, upgrade later

Business, £349 a monthUnlimited brands, 2,000 claims, every integration, the shopper claims page, returns and the API

Enterprise, talk to usCustom integrations, agreed limits, invoiced billing

Two months free on annual billing. Brands using a portal through their 3PL pay nothing at all. See the full comparison.

Send us the claim that is still open.

We will connect your warehouse system to a sandbox and close it in front of you, on your own data, so you can judge Claim Core rather than watch a scripted tour. If it does not help, say so and we will leave it there.

Start on the free plan Book a demo