Jira, Asana, Coda — keep procurement and ops aligned
PO/quote/shipment events stream to Jira, Asana or Coda — your operating system stays the source of truth in Italy.
Jira — issue per PO with status transitions
Each PO creates a Jira issue in the project of your choice. Status transitions (Quoted → Approved → In Production → Shipped → Delivered) map to workflow. Comments two-way; attachments (artwork, invoice PDFs) sync.
Asana — task per PO, due dates from milestones
Each PO becomes an Asana task with sub-tasks for milestones (sample approval, production start, ship date, delivery). Due dates pulled from our timeline — your team sees what's coming up.
Coda — table-driven dashboards
Coda pulls PO data via API into your tables — combine with budget, headcount, event calendar. Pack provides ready-built views: "this quarter's POs", "by department", "shipments this week".
Italy — local data and IVA 22%
Invoices via SdI (Sistema di Interscambio) carry the Jira/Asana/Coda issue/task ID in line description — easy reconciliation with IVA 22% reports. Milano hub staff also see the issue ID for context.
FAQ
OAuth or API token?
Both — OAuth 2.0 for user-context actions; service tokens for automated sync.
Custom field mapping?
Yes — map our fields (department, cost centre, event, urgency) to your custom fields on the issue/task.
Webhooks reverse direction?
Yes — status change in Jira/Asana can trigger actions on our side (cancel, request hold, request expedite).
Coda Pack maintained?
Yes — published in Coda Pack gallery, updated quarterly.
Multiple projects/workspaces?
Yes — route by department, country, or business unit to different Jira projects or Asana workspaces.