Carrier Corrections

Overview

Carrier Corrections turns a supported carrier invoice CSV into reviewed shipping-label corrections and, when selected, merchant charges. The workflow preserves the source invoice, matches each correction to a shipping label and merchant, applies the merchant's correction-pricing policy, and records every material transition in the audit log.

The initial supported format is UPS Invoice Summary CSV.

Before You Begin

You need permission to read charges to view correction imports and permission to write charges to upload, edit, discard, or apply them.

Confirm that:

• The CSV is a supported carrier invoice export, not a manually edited spreadsheet.
• Shipping labels use the same currency as the correction invoice.
• Each merchant has an active relationship with your team.
• Carrier Correction pricing is configured for the team or merchant.

Carrier corrections pass through at cost by default. A team or merchant can instead reuse the original shipping multiplier or use a dedicated correction multiplier.

Import a Carrier Invoice

1. Open ShipOS → Shipping → Carrier Corrections (opens the Cybership dashboard in a new tab).
2. Select or drop the carrier invoice CSV.
3. Wait while ShipOS verifies the upload, detects the format, and analyzes its rows.
4. Open the resulting draft from Import history.

Source CSVs are retained for 30 days. Discarding an import removes its source immediately unless a submitted support request requires retention. Check the audit log for source-file deletion.

Review Correction Rows

Each normalized row shows its review state, label match, merchant, carrier correction, merchant correction, and source details.

Use the table views and filters to work through the draft:

• Needs resolution contains every row that blocks Apply.
• Resolved contains rows explicitly included or skipped.
• Included rows create merchant charges.
• Skipped rows remain in the audit history and do not create charges. A skipped row that has a deterministic label match still records the carrier correction on that label.
• Already processed identifies corrections whose canonical identity was applied by an earlier import.

Apply remains blocked while any row is unresolved. Open a blocking row and either select a compatible shipping label, include the resolved correction, or explicitly skip it.

How Matching Works

ShipOS starts with the correction tracking number, then checks carrier compatibility, currency, merchant relationship, and the original shipping charge. A row can require manual review when there is no label, more than one compatible label, more than one original shipping charge, a currency mismatch, or no billable merchant.

Changing the matched label recalculates the merchant, original charge, pricing method, multiplier, and merchant correction. Manual merchant-amount overrides require a reason and remain visible in the audit log.

Review Merchant Charges

The Merchant charge summary groups all included corrections by merchant. It shows:

• Correction count
• Total carrier correction
• Total merchant correction

These are uninvoiced charges. The merchant's next applicable invoice cycle captures them automatically.

Before applying, the confirmation dialog calls out skipped unmatched rows, included credits, and manual overrides. Required acknowledgements prevent accidental billing.

Apply the Draft

1. Resolve or skip every blocking row.
2. Select Review and apply.
3. Confirm the detected format and any displayed warnings.
4. Select Apply corrections.

Application is idempotent. Retrying an interrupted job does not create duplicate merchant charges, and a correction already applied by another import is labeled Already processed.

An import with no included rows can still be applied after every row is explicitly skipped. No merchant charges are created, but matched labels retain the confirmed carrier correction.

Find Corrected Shipping Labels

The Shipping Labels table shows a Corrected badge and provides a Corrected filter whenever a carrier correction has been recorded. Open a corrected label and select the Corrected tab to see its source CSV, carrier invoice, correction reason, original carrier cost, signed carrier adjustment, corrected carrier cost, and confirmation time. The source filename links back to the import, where users with charge access can download the retained sheet.

Each label stores only the latest confirmed correction snapshot. Applied import lines remain the complete historical record, so applying a later correction updates the label summary without deleting earlier import history.

Manage Applied Correction Charges

Applied corrections appear with the merchant's other uninvoiced charges. They support the standard charge actions: view, update, and delete, plus removal from a draft invoice when applicable.

Updating an imported correction preserves its source-import provenance for audit history while replacing the editable pricing values. Manually created Shipping Correction charges use the same pricing fields without inventing CSV import or source-row identifiers.

Unsupported CSV Formats

If ShipOS cannot recognize the export, the import is marked unsupported and no correction rows are created. You can:

• Download the retained source CSV.
• Submit a support request with a short description of the export.
• Discard the import if no support request has been submitted.

Submitting a support request retains the source CSV for Cybership support to evaluate the format.

Audit and Troubleshooting

Open the Audit log tab to see upload, detection, review, application, support, and source-retention events. Expanded user-triggered events include the operator as a linked User in the structured event details. System-triggered events do not include a User reference.

Common blocking states:

If application stops partway through, use Retry application. ShipOS resumes from the persisted row state and retains the same duplicate-protection guarantees.