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

CHANGELOG

What we have shipped, and when.

Newest release first. Each one lists what was added, what was improved and what was fixed, written in the words of the people who use it rather than the ticket numbers behind it.

The key

  • Added, new in that release
  • Improved, something that already worked
  • Fixed, something that did not

v2.1

Five more warehouse systems, returns on accepted claims, and more evidence on every claim

Beta. ShipHero, Mintsoft, Clarus, Deposco and Linnworks are built and tested against each system's published API and our own test accounts, behind the same screens as Helm. None is yet running for a customer in production, so we connect the first customers on each one ourselves and watch the first weeks with them. The badge comes off as soon as a customer is live.

Added

  • ShipHero. Connect a 3PL or brand ShipHero account with a developer user's refresh token, map brands to customer accounts, and have despatched orders, tracking and delivery status, holds, serial and lot numbers, and totes and picks attached to claims. Claim Core registers the despatch webhook for you
  • Mintsoft. Connect with an API key, map brands to Mintsoft clients, and have despatched orders, tracking, batches and serials, box contents, order documents and warehouse notes on every claim. Claim evidence can be sent to the order, and returns are recorded in Mintsoft with receipt read back; return labels are uploaded by your team, since Mintsoft does not issue them
  • Clarus. Connect a Clarus tenant with a dedicated API user, map brands to its accounts, and have despatched orders, tracking numbers, the picking record with tote and bin, serial numbers and the people who picked, packed and despatched attached to claims. Claim Core registers the despatch automation, or shows you the address to add
  • Deposco. Install Claim Core's Deposco application in your environment, map brands to Deposco companies, and have shipped orders with per-parcel tracking, lots, serials and warehouse notes on every claim. Returns are opened in Deposco with receipt read back; return labels are uploaded by your team, since Deposco does not issue them
  • Linnworks. Install Claim Core's Linnworks application from a link and the connection completes itself, map brands to sales channels when several share one account, and have processed orders with tracking, parcels, batches, serials, the audit trail and notes on every claim. Returns are booked in Linnworks with a return label from your courier where it can print one; claim evidence is sent to the order as a note
  • Returns: ask for the item back on an accepted claim and the shopper gets a return label in the brand's name, issued by the warehouse system where it can (ShipHero today) and supplied by your team where it cannot, with written instructions as a fallback. Receipt is recorded on the claim, and an automation action can approve and ask for the item back in one go. Business and Enterprise
  • More from the warehouse system on every claim: holds on the order (with an automation condition and a self-service limit to match), serial and lot numbers on each line, picking records with tote and bin, and the files the warehouse holds against the order. Claim evidence can be sent back to the order where the system accepts it

Improved

  • Every integration now looks the same: the same connect card, manage page, brand mapping and claim evidence whichever warehouse system is behind it. Where a system cannot supply something, the claim page says "Not supported by" that system rather than leaving a blank
  • The return request form says whether the warehouse system will make the label or only record the return, so the team knows straight away when to upload one
  • The documentation's evidence table lists what each warehouse system supplies, feature by feature, and the integration reference has a section per system

Fixed

  • A despatch update that fails its signature or token check is now rejected outright rather than accepted as unsigned, and a redelivered update is acknowledged once instead of processed twice
  • A warehouse system connected for a 3PL no longer assigns every despatched order to the 3PL's only brand; each brand must be mapped to its own client, account or company first

v2.0

Self-service shopper claims: what they want, who decides, and where the limits are

Added

  • Shoppers now say what they would like: a refund, a replacement, or something else in their own words. Whoever decides records what was granted, and both sides show on the claim, in both lists and on the decision email
  • The shopper is emailed the outcome automatically the moment a claim is decided, in the brand's voice, with what they asked for and what was agreed. Nobody has to remember to send it, and it can never be sent twice
  • Choose per brand where a shopper's claim goes first: straight to your team, or to the brand's own admins, who decide it in the portal and can pass it to you with a reason when the warehouse needs to look
  • Self-service limits: a claim window after despatch, caps on order and item value, a cap on online claims per order, and which problems and resolutions shoppers can pick. Set once for the organisation, override per brand; shoppers outside the limits are asked to get in touch instead
  • Automation knows who raised a claim and what they asked for, so a rule can approve small shopper refunds on the spot and tell the shopper. Rules leave damaged, wrong or faulty items to a person, because a shopper cannot attach a photograph; those problems are routed to your team by email
  • A "Needs your decision" view and dashboard banner in the brand portal, and a "With brand" badge for your team
  • Brands that run their own warehouse can now sign up as a brand: your own claims page for your shoppers, your team deciding with the warehouse evidence attached, no 3PL in between
  • Shoppers can identify themselves with their mobile number as well as the delivery postcode or email address on the order

Improved

  • The shopper form checks each field on its own and keeps what was typed; the confirmation page says what was asked for
  • Claim page dialogs are announced to screen readers, move focus into the first field and close on Escape; toasts are read aloud
  • Uploaded evidence is stored and served as exactly what its bytes are, whatever the file was called

Fixed

  • A shopper-raised claim now reaches the team that decides it, and each side's email links to a page it can open
  • A rule such as "total value under 10, approve" no longer fires on a claim whose value is unknown

v1.9

Let your shoppers raise claims, and make the page your own

Added

  • Consumer claims page: let shoppers raise a claim themselves from a branded link, with no account needed. They find their order by order number plus the postcode or email on it, pick the item and what went wrong, and get a reference back
  • Each brand gets its own shareable link for the page, shown on the brand screen
  • Brand users are notified when a shopper raises a claim, and can email the outcome back to the shopper in your brand's voice once it's decided
  • Per-brand page configuration (org admins): set the page headline and intro, choose which details a shopper must enter (postcode and/or email) and how many, all with a live inline preview of what shoppers see
  • Per-brand logo and colour: give each brand's consumer page and portal its own logo and accent colour, with readable button contrast applied automatically
  • "Your tailored plan" panel on Billing for custom-plan customers: confirm your agreed price, billing method, and exactly what's included

Improved

  • One screen to manage a brand's consumer page (wording, required details, logo, colour and the shareable link) with the preview alongside
  • Brand logo and colour changes are now recorded in the audit trail

Fixed

  • Paid-plan features now activate only once payment is confirmed, so a selected plan and an active subscription can no longer drift apart

v1.8

In-app support tickets, Helm integration, session security and auto sign-out

Added

  • In-app support tickets: raise a ticket about Claim Core itself from either side of the app, with categories (account/access, claim issue, reporting, integration, billing, bug, other), priorities, statuses, and a separate reply thread per ticket
  • Up to 5 attachments per support ticket (10 MB each), with a styled file picker and per-file remove
  • Email notifications for support tickets: each event copies the configured Claim Core support inbox and, for brand-raised tickets, the 3PL's admins and ops staff
  • Internal staff notes on tickets: hidden from the brand portal, visible to 3PL staff and Claim Core admins
  • Automatic sign-out after inactivity: 30 minutes for 3PL users, 15 for brand users, 12-hour absolute cap on every session
  • Step-up re-auth for sensitive actions (billing, plan changes, team management), asking for a recent password instead of a full sign-out
  • "Remember this device" option that keeps your browser trusted for 30 days, skipping step-up prompts
  • Helm integration: install via the TDC Partners app store, no manual credential paste, because the install handshake provisions the connection end to end
  • Soft-delete a claim from the detail page (org admin only), so the row vanishes from lists and reports while the audit trail is preserved
  • Brand to Helm fulfilment-client mapping: order search now scopes by client id so an org with multiple brands in one Helm tenant can't cross-leak results
  • Richer billing page: usage-capacity panel with monthly cap, current usage, and remaining headroom; monthly/annual toggle on the plan grid

Improved

  • Paste-into-search now works on every list page, not just the create form. Order references pasted from emails, PDFs, and spreadsheets, invisible characters and odd dashes included, match the same way typing them does
  • Billing page reshuffled: plans grid lifted to the top, redundant "current plan" card retired
  • Order-reference matching is now consistent across Helm Legacy, Helm and Voila by sharing the same scrub pass on both the query and stored values

Fixed

  • Helm install callback no longer 500s on encrypted state with a product variant in the query string
  • Helm and Voila installs no longer redirect through the Helm Legacy tenant subdomain
  • Helm install success page now gates on auth instead of showing a misleading "connected" state for signed-out visitors
  • File uploads (claim evidence, support attachments) no longer fail when the storage path approaches its length limit
  • Subscription checkout pages now load without a Content-Security-Policy block
  • Subscription checkout failures now surface the specific error message returned during checkout instead of a generic banner

v1.7

Search-as-you-type, structured claim sidebar, deeper Helm integration

Added

  • Search-as-you-type order picker on the staff claim form: substring matches across order reference, customer name, postcode, tracking code, and Helm internal id
  • Helm Legacy integration fully wired: install the app, paste a Supervisor user's credentials, search any order in your tenant from the claim form
  • Customer panel on the claim detail page: name, email, phone, plus a count of prior claims from the same customer (matched by email or postcode)
  • Shipping address panel pulled from the warehouse order
  • Tracking and fulfilment panel: carrier, tracking number, the delivery status the warehouse system reports, picker, packer, dispatcher, and pack-station video where Helm has a recording
  • "Rest of the order" panel showing lines on the original warehouse order that aren't being claimed
  • "Prior claims for this order" panel with coloured status badges and links to past decisions
  • Five new claim types: Wrong item, Late delivery, Quality issue, Packaging damaged, Lost in transit
  • Helm integration diagnostic page in the platform admin: credentials check, scan trace, one-click order-reference field backfill

Improved

  • Unit values display as 2 decimal places instead of 4
  • Claim line items pre-populate from the warehouse order on claim creation
  • Sidebar panels now show every field with N/A fallbacks rather than disappearing when a field is empty
  • Warehouse enrichment is auto-fetched on claim creation so the detail page has tracking and customer info on first render
  • Order search now uses substring match across multiple fields, replacing the previous exact-match lookup

Fixed

  • 500 error on claim submission when the pricing-enrichment path fired
  • Helm webhook payloads weren't extracting any fields because of an envelope-wrapping change on the sender side
  • Misleading "No WMS reference matched" message that showed even when warehouse data was successfully fetched
  • Tracking section on the claim detail page no longer displays a raw Python dict

v1.6

White-label portal, self-serve billing, pack-station video, and platform admin

Added

  • White-label brand portal: your business name, logo, primary colour, and support email applied across the portal and emails
  • Custom domains for the brand portal: point a CNAME at Claim Core and we register the domain and provision SSL. Serving a custom domain needs us to add it on our side first, so it is set up with you rather than self-serve
  • Self-serve billing: plan upgrades and a customer portal for managing payment details, with subscription state kept live in sync
  • Pack-station video on the claim: when Helm has a recording for the order, watch it inline in the workbench
  • Multiple warehouse integrations per organisation, mapped per brand, so you can operate brands across more than one warehouse
  • Org admins can "View as a brand" to see exactly what a brand sees in the portal
  • Custom AI policy: write your own decisioning rules for AI Review instead of picking a preset
  • Polished signup and onboarding flow with plan recommendation

Improved

  • Transactional emails redesigned: clearer hierarchy, friendlier copy, branding-aware logo and accent colour
  • In-iframe disconnect button on the embedded Helm dashboard
  • Helm webhook ingest is more lenient: it now handles array payloads and works without a signing secret
  • Manual claim form surfaces validation errors instead of silently failing

Fixed

  • Invitation emails silently failing. Failures now surface inline in the UI
  • Em-dashes throughout the product replaced with clearer punctuation

v1.5

Reports and exports, automation rules, and documentation

Added

  • Four reports, as KPI tiles and tables: Claims Overview, Financial Summary, Courier Performance, and Brand Report
  • CSV exports on all reports and raw claims data (up to 10,000 rows)
  • Scheduled reports: delivered by email on a daily, weekly, or monthly schedule
  • Automation rules: auto-accept or auto-reject claims matching configurable criteria
  • Documentation section at /docs/
  • Changelog page

Improved

  • Claim detail view: separated internal notes and brand comments into distinct tabs
  • Claim header now shows claim type badges and financial totals at a glance
  • Timeline entries now show a clear [Internal] label for non-public notes

Fixed

  • Reporting namespace not registering on server restart
  • CSV exporter using incorrect get_full_name() attribute on custom User model

v1.4

Claim reopening, portal improvements, and UI redesign

Added

  • Claim reopening: Organisation Admins can reopen accepted or rejected claims
  • Awaiting Info status: pauses the decision clock while you are waiting on the brand to come back
  • Bulk claim actions: accept, reject, or change status on multiple claims at once
  • Brand portal claim detail view with status history and comments

Improved

  • Full UI redesign with Tailwind CSS: cleaner, faster, and more consistent across all pages
  • Dashboard redesigned with rich stat cards and recent activity feed
  • Claim list now shows SLA status inline with colour-coded indicators

Fixed

  • HTTPS detection behind the production load balancer no longer falls back to HTTP
  • Database migrations not running at startup in production