shoplazza CLI — orders module

CRITICAL — before anything else, use Read on ../shoplazza-common/SKILL.md. It owns every cross-cutting mechanic: the three access tiers, the output envelope (.data), --dry-run, --jq (incl. "don't pass -r"), --fields, schema, api rest, auth / profiles, and the safety protocol. This file covers only the orders domain and never repeats them.

Overview

The orders module manages the order lifecycle (search, count, get, create, update, cancel, pay, delete) and its sub-resources: fulfillments (shipping records), refunds, fraud risks, payment transactions, after-sales (post-sales) records, shipping zones/rates, and tracking carriers. All three access tiers apply (tier-selection rule is in shoplazza-common — prefer +shortcut).

Shortcuts exist for +search / +count / +ship / +refund / +update-tracking only — every other operation (get, cancel, create, pay, and all sub-resources) is a spec leaf. Orders is a large domain: this file is the router plus the high-frequency operations; per-sub-resource depth lives in references/.