Your shipping data knows far more than you think

Get an overview of whether delivery times have changed — overall, per market and per carrier — so you can quickly see whether anything needs your attention.
Analyse delivery times for the past 30 days and calculate the average delivery time per country and carrier.

Compare the result with the average level for the past year.
For every combination of sender country, destination country and carrier, show: number of shipments, average delivery time, difference in days and difference in per cent.
Highlight the combinations where the past 30 days deviate most negatively from the annual average, along with those that have got worse compared with the preceding 30-day period.

Only include combinations with enough shipments for a meaningful comparison, and state the threshold you are using.

Ask your AI assistant to review the invoices for a period and collect the lines that deviate from what was originally invoiced, so you can quickly see where the largest and most recurring discrepancies are — without having to hunt line by line yourself.
Review the invoices for the past 30 days and find corrections and post-adjustments relative to the amount originally invoiced.

Show the discrepancies in a table with: shipment reference, invoice number, carrier, original amount, new amount, difference in kroner, difference in per cent, and a short explanation of the cause (e.g. weight or dimension correction, road tax, manual handling, or something else).
Sort by the financial size of the discrepancy, and highlight both the largest individual discrepancies and the most recurring types.

Finish with a summary of the total financial impact per carrier.

Ask Claude to build a single overview of the shipments that have fallen out of the normal flow — delayed, never scanned or uncollected — so your colleagues in support can quickly see where there is something to act on.

Build an overview showing the shipments that have fallen out of the normal flow and therefore need follow-up.

Group the shipments by severity: critical (act now), under watch (approaching a critical level), never scanned, plus uncollected/returned shipments split by how far they are through the returns process.

For every shipment, show: parcel number, carrier, recipient city/country, severity, number of days since booking or the last scan, latest status, and a short human-readable explanation of why it is flagged.

Make it possible to filter by severity and carrier, and to search by parcel number or city.
Sort by severity by default, and make it visually clear which shipments are the most critical.

Instead of going into the platform yourself to adjust your checkout, you can ask Claude to make the change for you. Claude always shows you what it proposes to change before anything is saved, so you can approve it first.

Add a new delivery option to my checkout:[carrier and product], with the name "[name]" and the price[amount]DKK

Show me what the new delivery option will look like before you save it.
If something in the request does not exist or cannot be done, say so clearly instead of guessing.

The same approach works for adjusting a price, changing a pricing rule, or activating/deactivating an existing delivery option — just describe the change and ask to see it before it is saved.