pp-amazon-seller
Printing Press CLI for Amazon Seller. Read FBA inventory, orders, sales reports, listings, and catalog data for an Amazon seller account.
What this skill does
<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/commerce/amazon-seller/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
# Amazon Seller — Printing Press CLI
## Prerequisites: Install the CLI
This skill drives the `amazon-seller-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:
1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows:
```bash
npx -y @mvanhorn/printing-press-library install amazon-seller --cli-only
```
2. Verify: `amazon-seller-pp-cli --version`
3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill.
If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):
```bash
go install github.com/mvanhorn/printing-press-library/library/commerce/amazon-seller/cmd/amazon-seller-pp-cli@latest
```
If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds.
## Command Reference
**catalog** — Read Catalog Items API item data.
- `amazon-seller-pp-cli catalog get` — Get one catalog item by ASIN.
- `amazon-seller-pp-cli catalog search` — Search catalog items. Provide marketplaceIds plus one valid search mode such as keywords or identifiers with...
**fba-inventory** — Inspect Fulfillment by Amazon inventory summaries.
- `amazon-seller-pp-cli fba-inventory` — List FBA inventory summaries. For North America marketplace-level inventory, pass granularityType=Marketplace,...
**listings** — Read Listings Items API data for seller SKUs.
- `amazon-seller-pp-cli listings get` — Get one listing item by seller ID and SKU.
- `amazon-seller-pp-cli listings search` — Search listing items for a seller.
**orders** — Search and inspect Orders API v2026-01-01 order records.
- `amazon-seller-pp-cli orders get` — Get one Orders API v2026-01-01 order.
- `amazon-seller-pp-cli orders search` — Search orders. Provide exactly one of createdAfter or lastUpdatedAfter; Amazon returns 400 for invalid combinations.
**reports** — Create reports, poll report status, and inspect report document metadata.
- `amazon-seller-pp-cli reports create` — Create a report request. Prefer --stdin for JSON bodies so marketplaceIds remains a JSON array and reportOptions...
- `amazon-seller-pp-cli reports document` — Get report document metadata and the presigned download URL. This command does not download or open the document.
- `amazon-seller-pp-cli reports get` — Get one report by report ID. This is the manual polling endpoint for report processing status.
- `amazon-seller-pp-cli reports list` — List reports. If nextToken is set, Amazon requires it to be the only query parameter; pass no other filters with...
**inbound-plans** — Create and manage Fulfillment Inbound v2024-03-20 inbound plans.
- `amazon-seller-pp-cli inbound-plans create --marketplace-id ATVPDKIKX0DER --source-address address.json --items items.csv --name "June FBA"` — Preview a createInboundPlan body from CSV/JSON input. **Write command:** pass `--yes` to send, `--dry-run` to render the HTTP request, and `--wait` to poll the returned operation.
- `amazon-seller-pp-cli inbound-plans create --stdin` — Read Amazon's exact createInboundPlan JSON request body from stdin. **Write command:** pass `--yes` to send.
- `amazon-seller-pp-cli inbound-plans status --operation-id <operationId> --wait` — Poll getInboundOperationStatus for asynchronous Fulfillment Inbound POST/PUT operations.
- `amazon-seller-pp-cli inbound-plans get <inboundPlanId>` — Get one inbound plan.
- `amazon-seller-pp-cli inbound-plans list --status ACTIVE --page-size 10` — List inbound plans.
- `amazon-seller-pp-cli inbound-plans cancel <inboundPlanId> --yes` — Cancel an inbound plan. **Write command:** requires `--yes` unless `--dry-run` is set.
- `amazon-seller-pp-cli inbound-plans packing generate --inbound-plan-id <id>` — Generate packing options. **Write command:** use `--dry-run` for request preview.
- `amazon-seller-pp-cli inbound-plans packing list --inbound-plan-id <id>` — List packing options.
- `amazon-seller-pp-cli inbound-plans packing confirm --inbound-plan-id <id> --option-id <packingOptionId> --yes` — Confirm a packing option. **Write command:** requires `--yes` unless `--dry-run` is set.
- `amazon-seller-pp-cli inbound-plans packing set --inbound-plan-id <id> --body cartons.json --yes` — Set carton-level packing information. **Write command:** requires `--yes` unless `--dry-run` is set.
- `amazon-seller-pp-cli inbound-plans placement generate --inbound-plan-id <id> --body placement.json` — Generate placement options, optionally with customPlacement JSON. **Write command:** pass `--yes` when providing a body to send instead of previewing.
- `amazon-seller-pp-cli inbound-plans placement list --inbound-plan-id <id>` — List placement options.
- `amazon-seller-pp-cli inbound-plans placement confirm --inbound-plan-id <id> --option-id <placementOptionId> --yes` — Confirm a placement option. **Write command:** requires `--yes` unless `--dry-run` is set.
- `amazon-seller-pp-cli inbound-plans transportation generate --inbound-plan-id <id> --body transportation.json` — Generate transportation options from placement/shipment JSON. **Write command:** pass `--yes` when providing a body to send instead of previewing.
- `amazon-seller-pp-cli inbound-plans transportation list --inbound-plan-id <id> --placement-option-id <placementOptionId>` — List transportation options.
- `amazon-seller-pp-cli inbound-plans transportation confirm --inbound-plan-id <id> --body selections.json --yes` — Confirm transportation selections. **Write command:** requires `--yes` unless `--dry-run` is set.
For CSV item input, use columns `msku,quantity,prepOwner,labelOwner,expiration,manufacturingLotCode`. For the US marketplace `ATVPDKIKX0DER`, the CLI warns when `prepOwner=AMAZON` or `labelOwner=AMAZON`, because Amazon says US FBA prep and item label services are no longer available starting January 1, 2026.
**profitability** — Compute estimated SKU profitability from Amazon reports.
- `amazon-seller-pp-cli profitability sku-pnl --marketplace-id ATVPDKIKX0DER --days 30` — Estimate per-SKU revenue, fees, storage cost, margin, and profit.
- `amazon-seller-pp-cli profitability fee-breakdown --marketplace-id ATVPDKIKX0DER` — Show itemized estimated referral, FBA, closing, and total fee percentages.
- `amazon-seller-pp-cli profitability settlement-reconciliation --marketplace-id ATVPDKIKX0DER --days 90` — Compare order revenue to completed settlement rows and flag discrepancies.
- `amazon-seller-pp-cli profitability reimbursements --marketplace-id ATVPDKIKX0DER --days 90` — Aggregate reimbursements by SKU and reason.
**inventory-intel** — Compute FBA inventory health, restock, aging, and fulfillment recommendations.
- `amazon-seller-pp-cli inventory-intel health-score --marketplace-id ATVPDKIKX0DER` — Score inventory health per SKU.
- `amazon-seller-pp-cli inventory-intel restock --marketplace-id ATVPDKIKX0DER --lead-time-days 14` — Estimate stockout timing and reorder quantities.
- `amazon-seller-pp-cli inventory-intel stranded --marketplace-id ATVPDKIKX0DER` — Surface stranded inventory rows and recommended actions.
- `amazon-seller-pp-cli inventory-intel aging --marketplace-id ATVPDKIKX0DER --warn-days 150` — Forecast long-term storage fee risk.
- `amazon-seller-pp-cli inventory-intel fba-vs-fbm --marketplace-id ATVPDKIKX0DER --estimated-shipping-cost 5` — Compare estimated FBA vs FBM per-unit profit.
**sRelated in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.