fst-procurement

Guides procurement workflows for purchase orders, container tracking, and warehouse receiving in FST.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill fst-procurement-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fst-procurement
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/fst-procurement
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill fst-procurement-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working on the FST/Otgruzka procurement module requires knowing its exact domain rules: purchase order statuses, container tracking limits, and warehouse receiving constraints. This Skill encodes those rules so changes to the procurement codebase stay consistent with the product model and never break Firestore data integrity. ## Core Features & Use Cases - Purchase Order Lifecycle Rules: Enforces the ЗЗ (purchase order) status flow from draft to arrived, including the rule that received is only set after warehouse acceptance, never by carrier sync. - Warehouse Receiving Guardrails: Ensures receiving writes proper stock movements with purpose: 'purchase' and the order number, and forbids deleting posted orders or moving stock from drafts. - Container Tracking Constraints: Documents Maersk/MSC tracking integration limits, including the lack of /api sync on Vercel production. - Use Case: When asked to add an auto-status update from carrier tracking, the Skill reminds you the maximum auto-status is arrived and that received requires explicit warehouse acceptance. ## Quick Start Ask the AI to review or modify the FST procurement module, for example to add a new purchase order status or fix the receiving flow, and it will apply these rules.

Frequently Asked Questions about fst-procurement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a purchase order status in the FST procurement module?▼

Edit the status definitions in src/lib/procurement/types.ts and status.ts, keeping the draft-to-arrived flow intact. The received status must only be set after warehouse acceptance, never automatically from carrier tracking sync.

How does warehouse receiving work for purchase orders?▼

Receiving goes through receivePurchaseOrderInStore in src/lib/procurement/receive.ts, which writes a stock movement with purpose 'purchase' and the order number as comment. Draft orders never move stock, and posted orders can only be cancelled, not deleted.

Can carrier tracking automatically mark an order as received?▼

No. Carrier sync from Maersk or MSC tracking can set the status at most to arrived. The received status requires explicit warehouse acceptance or a deliberate manual status change.

Does container tracking sync work on the Vercel production deployment?▼

Usually not. The Vercel deployment often lacks the /api server routes under server/tracking, so automatic tracking sync cannot be promised on web production without a backend server.

Should I build RFQ or supplier quotation features for this procurement module?▼

No. The FST product model deliberately excludes RFQ, quotations, and accounts-payable invoicing from the full ERPClaw procure-to-pay flow. Only build them if explicitly requested.