Purchase Orders

The full PO lifecycle: orders and line items, additional costs, supplier quotations, payment schedules, notes, movement allocation, and change history.

21 tools — 12 read, 7 write, 2 delete.

Tool	Access	What it does
`purchase_order_add_note`	Write	Add a note or comment to a purchase order for team communication and documentation. Each call creates a new note entry (append model) — previous notes are preserved in storage but purchase_order_get_note only returns the latest one.
`purchase_order_delete`	Delete	Archive a purchase order by its ID (soft-delete — marks as archived, not permanently removed).
`purchase_order_get_by_id`	Read	Retrieve full details of a single purchase order by its ID, including products, supplier, dates, costs, and shipment links.
`purchase_order_get_costs`	Read	Retrieve actual incurred additional costs for a purchase order — freight, customs, duties, inspection, insurance — with per-product cost allocations.
`purchase_order_get_history`	Read	Retrieve the audit history of changes made to a purchase order — timestamps, users, change types, and optionally full PO snapshots at each change point.
`purchase_order_get_note`	Read	Retrieve the latest note for a purchase order — returns only the most recent note even if multiple exist (sorted by id desc).
`purchase_order_list`	Read	Retrieve a paginated list of purchase orders with filtering and sorting. No prerequisites — can be called directly.
`purchase_order_list_cost_names`	Read	Retrieve all unique additional cost type names used across all purchase orders — returns a flat string array only, no amounts. Use as a dropdown or autocomplete source when adding costs, or before calling purchase_order_save_costs to suggest consistent names.
`purchase_order_movement_delete`	Delete	Delete ALL product movements for a purchase order — removes the entire allocation at once, not individual records. There is no tool to delete a single movement — only all at once.
`purchase_order_movement_get_allocation`	Read	Retrieve the current product allocation state for a purchase order as a Sankey flow graph, showing how products flow between locations (supplier, port, warehouse, FBA).
`purchase_order_movement_get_history`	Read	Retrieve movement history for a specific purchase order and destination pair — a chronological log of product allocations to that location. Unlike purchase_order_movement_get_allocation which shows current state, this returns historical records.
`purchase_order_movement_save`	Write	Record a product allocation (movement) for a purchase order — assigning products to flow from one location to another in the logistics chain (supplier to port to warehouse to FBA).
`purchase_order_payment_check_status`	Write	System-wide action that scans ALL purchase order payments across the organization and marks overdue ones — this is a write operation despite its name.
`purchase_order_payment_get`	Read	Retrieve payment records for a specific purchase order, including both order payments (to supplier) and shipping payments (to freight forwarder).
`purchase_order_payment_get_calendar`	Read	Retrieve a calendar view of all purchase order payments for a given year, aggregated across all POs — useful for cash flow planning.
`purchase_order_payment_save`	Write	Save or update payment records for a purchase order — manages both order payments (to supplier) and shipping payments (to freight forwarder).
`purchase_order_quota_get`	Read	Retrieve pre-order freight forwarder quotation estimates for a purchase order — these are cost estimates for comparison, not actual incurred costs.
`purchase_order_quota_save`	Write	Save or update freight forwarder quotations for a purchase order.
`purchase_order_save`	Write	Create a new purchase order or update an existing one (upsert). If the payload includes an id field the existing PO is updated; otherwise a new PO is created.
`purchase_order_save_costs`	Write	Save or update additional costs for a purchase order.
`purchase_order_validate_key`	Read	Verify whether a purchase order upload key is still active (not expired) and return its associated PO, organization, and expiration date. This tool only validates — upload-key generation is done via the UI/public supplier portal, not via MCP.