Carrier Charge Normalizer

Use this skill when a seller has exported logistics charges from more than one platform or carrier and needs a stable local JSON structure before reconciliation.

Inputs

• - A local JSON file with a records array.
• Optional aliases for order id, shipment id, service, currency, weights, dimensions, base charge, surcharge, and billed charge.

Outputs

• - normalized_carrier_charges.json with canonical fields, source row, missing fields, and non-secret original references.

Rules

• - Preserve amounts and units; do not infer a currency or silently convert units.
• Keep unknown fields in extra_fields and mark them for review.
• Never include passwords, cookies, tokens, payment data, or customer raw personal data.
• This is a local preparation step. It does not call a marketplace, carrier, bank, or support system.

Acceptance

Run the sample and confirm canonical shipment ids, amounts, missing-field flags, and deterministic JSON output. A missing identifier must be reported, not invented.