Track a physical card's delivery
Tracks a physical card order's delivery status: shipping, tracking, delay.
AP Manager๐ Ad hocBeginnerRead-only
Ask it like this
Where is the physical card ordered for this employee?
When to use it
When an employee is waiting for a physical card and asks where it is.
What it produces
Order state (to ship, shipped...), tracking link, delivery city/country, estimated receipt date.
How it works
- 1Finds the card and its order
- 2Gives the shipping state and the delivery city
- 3Provides the tracking link when there is one
- 4Flags a possible delivery delay
- 5Checks the card's status to confirm it was received
What protects you
- This skill only reads: it changes nothing in Spendesk
- It acts with your permissions and your role, never beyond
- The assistant cannot approve or pay
โธTechnical detail60/100 ยท 1 tools
Cardsget_card_order
# Tracking a physical card's delivery
## Expected error on a non-physical card
`get_card_order` returns an explicit error if the card was never physically ordered โ true for any virtual card, and confirmed live on several long-active physical cards on this account (already activated, no order in progress). An error here **does not mean the card doesn't exist** โ it means there's nothing to track on the delivery side for this card at this stage. Check `get_card`/`list_cards` first to confirm the card exists and its status before calling this tool.
## Call
```json
{
"tool": "get_card_order",
"params": {
"companyId": "<companyId>",
"cardId": "<cardId>"
}
}
```
## Fields returned
`state` (`to_pickup`, `to_ship`, `shipped`), delivery city/country (not the full address โ direct the user to the Spendesk app if they need the exact address), `trackingLink`, `shippedAt`, `receivedAt`, `createdAt` (order date), `consideredAsLost`, `estimatedReceivedAt`.
โ ๏ธ `consideredAsLost` is computed at read time: it is `true` when `receivedAt` is null and the order is more than 30 days old. It is a delivery-delay heuristic, not the card's "Lost" status โ never tell the user a card is lost from it. `receivedAt` is not reliably recorded: to know whether the card was received, read its status via `get_card` (Active, Blocked or Ready = received). `city`, `country`, `trackingLink`, `shippedAt`, `receivedAt` and `estimatedReceivedAt` can each be null: read shipping progress from `state`.
## Difference from the cardOrder field on get_card
`get_card`/`list_cards` expose the same `cardOrder` object (same fields), but **only while the card is physical AND in "Pre-activated" status** โ as soon as the card is activated, that field disappears from the response. `get_card_order` stays available even after activation, to retrieve order history for a card already in service.
## Example user prompts
- "Where's the physical card ordered for [employee]?"
- "Is this card order running late?"
- "Give me the tracking link for [employee]'s card"
How to install this skill
/
- 1Download the file
s69-suivi-livraison-carte-physique.mdusing the button above. - 2Place the file in the
.claude/directory of your project (or~/.claude/for a global install).cp s69-suivi-livraison-carte-physique.md .claude/s69-suivi-livraison-carte-physique.md - 3Use in Claude Code โ the skill is automatically discovered. Describe your need in natural language and Claude will apply the skill instructions.
๐ก Make sure the Spendesk MCP is configured in your
.claude/settings.json with the tools get_card_order.Similar skills
โ
Top