Shopify fulfillmentShipment notifications.
Connect Shopify fulfillment, shipment tracking, and customer notifications through a database-backed queue with checks and recovery monitors.
- n8n
- Shopify
- AfterShip
- Supabase
- Gmail
- Telegram
- Order received
- Fulfillment checked
- Tracking synchronized
- Customer notified
What this means for your business
- Problem
- Fulfillment checks, shipment tracking, and customer updates involve repeated work across several tools.
- Solution
- Connect order checks, shipment tracking, and queued customer notifications, with alerts when work needs attention.
- Benefit
- Helps reduce manual handoffs and keeps customers informed about their shipments. Actual time savings have not been measured.
Durable outbox · recovery monitors
Challenge & system design
The challenge
Fulfillment, tracking updates, and customer communication span multiple tools. Manual handoffs create coordination work, while retries risk repeating actions that have already succeeded.
The solution
The system connects Shopify fulfillment to AfterShip tracking and a database-backed notification queue. Staff provide tracking details, automated checks control fulfillment, and monitors surface work that needs attention.
Engineering decisions
Check before committing.
Database intake claims and fulfillment locks coordinate processing. Orders with anything other than one eligible fulfillment order are routed for review.
Recover without guessing.
When an external action succeeds but local persistence is uncertain, reconciliation checks external state before retrying. A durable outbox separates event intake from notification delivery.
Keep communication controlled.
HMAC-validated shipment webhooks feed seven notification templates. Recipient details come from trusted database records, with test and live send gates.
Architecture & workflows
Fulfillment & shipping confirmation
The main fulfillment canvas connects order intake, fulfillment checks, database state, and staff notifications.
Tracking intake validation
Validates tracking registration requests and loads the trusted recipient before passing work to registration.
Tracking registration
Coordinates registration claims, AfterShip requests, database completion, and failed-registration review.
Shipment status updates
Validates webhook signatures, normalizes tracking events, and queues updates for customer communication.
Webhook validation close-up
Detail view of signature checking, raw JSON extraction, event normalization, and tracking-update intake.
Notification outbox worker
Processes queued notifications through send and verification paths, then updates delivery state.
Six recovery workflows
An operations overview showing notification-claim, outbox, fulfillment, registration, and tracking recovery routines.
Evidence & limitations
The case study documents 11 workflows, 185 nodes, a notification worker, and six watchdogs. These describe implementation scope; they are not a production performance benchmark.
33 to 60 hours / month
Based on client-reported 500 to 600 monthly orders and an assumed 4 to 6 minutes of manual work per order. Actual savings have not been measured.
Limitations & next steps
Database function internals and complete production execution evidence were not included in the supplied materials. Production impact still needs measurement.
WORKFLOW OUTPUTS · CONTROLLED TESTS
Customer updates and operational tracking.
Generated using test orders and simulated shipment events. The emails below show the same test order; the spreadsheet is a separate monitoring example.
These screenshots demonstrate sample outputs, not actual customer deliveries or measured production results. Execution logs are no longer available.
Shipment confirmation
The shipment email presents the shipped status, a tracking link, and the items in test order #1068.
Out-for-delivery update
A second email for the same test order presents the out-for-delivery status, sample location, and updated progress indicator.
Fulfillment monitoring
A separate test dataset shows shipped records with resolved recovery statuses and a pending shipment marked escalated after two reminders. These rows are not matched to the email examples above.
