OPS ► PACKAGE — multi-carrier shipping

One skill, seven carriers. The router picks the carrier automatically based on which credentials are configured.

Which carrier do I get?

--carrier <name>

Preference order:

myparcel

sendcloud

dhl

postnl

dpd

ups

fedex

Credential resolution

Each carrier resolves its credential(s) from, in order:

1. Environment variable(s) listed below.

2. preferences.json

   key (lowercase of the env var name) at

   ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json

   .
3. Doppler:

   doppler secrets get <NAME> --plain

   .

MYPARCEL_API_KEY

SENDCLOUD_PUBLIC_KEY

SENDCLOUD_PRIVATE_KEY

DHL_PARCEL_USER_ID

DHL_PARCEL_KEY

POSTNL_API_KEY

POSTNL_CUSTOMER_CODE

POSTNL_CUSTOMER_NUMBER

DPD_DELIS_ID

DPD_PASSWORD

UPS_CLIENT_ID

UPS_CLIENT_SECRET

UPS_SHIPPER_NUMBER

FEDEX_CLIENT_ID

FEDEX_CLIENT_SECRET

FEDEX_ACCOUNT_NUMBER

Routing

All API calls are delegated to

${CLAUDE_PLUGIN_ROOT}/skills/ops-package/ops-package.sh

carriers

ship

label

track

list

ship

Required:

--to "<address>"

"Person / Company, Street 12A, 1011AB Amsterdam, NL"

• / Company

  segment is optional.
• Postcode accepts with/without space; NL postcodes are normalised to uppercase without space.
• Country defaults to NL; common names (Netherlands, Belgium, Germany, France, UK, USA) map to ISO codes.

Flags (not every carrier honours every flag — unsupported flags are safely ignored per adapter):

• --from "<address>"

  override sender; default is the account's configured sender.

• --weight <grams>

  integer grams.

• --package-type 1|2|3

  1=parcel (default), 2=mailbox, 3=letter (MyParcel only).

• --signature

  require signature on delivery.

• --insurance <EUR>

  integer EUR; 0 disables (MyParcel only).

• --description "<text>"

  label reference (carriers differ; ~45 char max).

• --pickup

  request home pickup at sender (MyParcel only).

Invocation

${CLAUDE_PLUGIN_ROOT}/skills/ops-package/ops-package.sh \
  [--carrier myparcel|sendcloud|dhl|postnl|dpd|ups|fedex] \
  ship --to "$TO" [--from "$FROM"] [--weight "$W"] \
       [--signature] [--insurance "$INS"] [--description "$DESC"] \
       [--package-type "$TYPE"] [--pickup]

Returns:

{"carrier": "<name>", "shipment_id": "<id>", "response": { /* raw carrier JSON */ }}

Summarise to the user as:

Shipment created — <carrier> #<id>
Next: /ops:ops-package label <id>  to download the PDF.

Offer via

AskUserQuestion

• [Download label now]

  — call

  label <id>

  immediately

• [Track it]

  — call

  track <id>

• [Ship another]

• [Done]

label

<shipment-id>

${CLAUDE_PLUGIN_ROOT}/skills/ops-package/ops-package.sh label "$ID"

Behaviour per carrier:

• MyParcel: PDF saved to

  /tmp/myparcel_label_<id>.pdf

  and opened on macOS. If unpaid, returns

  {"status":"payment_required","payment_url":"..."}

  and opens the MultiSafepay URL.
• Sendcloud: Fetches the CDN PDF URL (v2

  /labels/<id>

  ) and saves locally.
• DHL NL: Fetches

  /labels/<id>?format=PDF&printerType=A4

  .
• DPD: Fetches

  /v1/parcellabelnumber/<id>?paperFormat=A4

  .
• PostNL / UPS / FedEx: PDF is returned inline with the

  ship

  call and cached to

  /tmp/<carrier>_label_<id>.pdf

  . Calling

  label

  re-opens that cached file. If the cache is gone, re-run

  ship

  (none of these carriers expose a stable label-recovery endpoint here).

track

<shipment-id>

Returns a normalised object across all carriers:

{"carrier":"<n>","id":"<id>","status":"<s>","barcode":"<b>","tracking_url":"<u>","recipient":<o>,"updated":"<ts>"}

list

MyParcel

Sendcloud

{"shipments":[],"note":"..."}

carriers

Prints which carriers are configured (

✓

·

--carrier

Error handling

• No carrier configured → script exits 2 with a checklist of envs. Surface it verbatim, then via

  AskUserQuestion

  :

  [Paste key now]

  [Open carriers doc]

  [Skip — configure later]

  On "Paste key now", collect via

  AskUserQuestion

  free-text and write to

  preferences.json

  .
• 4xx from carrier → dump the JSON error body and stop. Do not retry silently.
• Address parser looks wrong → re-prompt the user with the parsed breakdown and ask for corrections before POSTing.

Verification status

Unverified adapters are tagged with

# UNVERIFIED - pending live test with account