Fulfillment Input Normalizer

Use this skill before reviewing multi-location order routing or when platform exports use different field names.

Inputs

• - A local JSON file with orders, locations, and optional rules arrays.
• Quantities must be non-negative numbers and location identifiers must be stable within the file.

Outputs

• - normalized_fulfillment_inputs.json with canonical orders, locations, rules, missing fields, and conflict flags.

Rules

• - Preserve the supplied inventory snapshot time and do not claim it is real-time.
• Do not infer inventory availability, delivery distance, or platform priority when absent.
• Keep conflicting rules visible and report them for review.
• Never include passwords, cookies, tokens, customer raw personal data, or live API responses.

Acceptance

Run the sample and confirm order lines, location inventory, priorities, and missing-rule flags are deterministic. A malformed quantity must be reported, not repaired silently.