SRV-34 — V2 — Carrier API & WhatsApp Business integrations

SummaryCopy Anchor Link

Shipment creation and tracking webhooks with the selected carrier(s); WhatsApp Business templates for confirmations and reminders.

DescriptionCopy Anchor Link

Carrier API integration and the WhatsApp Business API are V2 (cahier §11, §14.2; DLV-05, NOT-08). In V1, carriers are assigned manually with a tracking number and WhatsApp is only a share link and the regional support button. This task adds a carrier adapter interface (create shipment, label, cancel, tracking webhooks with signature checks) implemented for the carrier(s) HOCO selects, maps carrier statuses to DeliveryStatus, and adds a WHATSAPP channel adapter to the notification service using approved WhatsApp Business templates for order confirmations, status updates and payment reminders, with opt-in tracking and per-conversation cost monitoring. Out of scope: changes to the regional support routing (V1, SRV-24).

SubtasksCopy Anchor Link

DeliverablesCopy Anchor Link

• apps/server/src/modules/integrations/carriers/{adapter.ts,<carrier>.ts,webhooks.router.ts}
• apps/server/src/modules/notifications/adapters/whatsapp.ts
• Approved WhatsApp template list and carrier integration notes in /docs/srs/integrations

Acceptance criteriaCopy Anchor Link

• Marking an order READY with an API carrier creates the shipment and stores the tracking number automatically (DLV-05)
• A carrier delivered webhook moves the delivery and the order to DELIVERED once, even if sent twice (DLV-05)
• A reseller who opted in receives the WhatsApp template when the order is confirmed; one who did not receives none (NOT-08)
• A carrier API outage switches the delivery to manual mode and alerts the delivery manager

Requirements coveredCopy Anchor Link

API surfaceCopy Anchor Link

Test measuresCopy Anchor Link

• Contract tests against the carrier sandbox
• Webhook replay and signature tests
• WhatsApp sandbox test with template messages

RisksCopy Anchor Link

• Carrier APIs and WhatsApp template approvals take time and cost per message — start provider onboarding at the start of P4 and keep manual modes available

KPICopy Anchor Link

• Delivered by Sun 7 Feb 2027 within 3 person-day(s).
• Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
• Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

---

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.