CyberFreezeDev
Loading
Shopify order events confirm COD orders, send tracking, match payments, book sales and correct stock.
Shopify runs the storefront and checkout. The integration handles what happens after Place order.
The integration listens to store webhooks and acts on each: COD confirmation, tracking links, refunds into the books and stock corrections.
A Shopify integration with WhatsApp, payments and your books listens to the store's webhooks and acts on each one. A new cash on delivery order asks the customer to confirm on WhatsApp before it is packed. A fulfilment sends the tracking link. A refund updates the books. A stock change from a sale on another channel corrects the Shopify count.
If you need the store itself built or fixed, that is web engineering. If you need campaigns to bring traffic, that is growth marketing. This page is the plumbing between the store and everything else, and it is the work behind most of what we do for retail and e-commerce brands.
COD customers confirm, change address or cancel on WhatsApp before the order is packed.
On orders/create with a cash on delivery gateway, the customer gets a WhatsApp template with Confirm, Change address and Cancel buttons. The reply is written back to the order as a tag or note, and unconfirmed orders are held before dispatch. Built on our WhatsApp integration and WhatsApp CRM.
Tracking number and courier link sent as a template when an order ships.
fulfillments/create and fulfillments/update send the tracking number and courier link as a utility template, which removes most "where is my order" chats.
Order ids passed to the gateway so Razorpay settlements break down by order.
Shopify order ids are passed through to the payment gateway so a Razorpay settlement can be broken down to the orders, refunds and fees inside it.
Paid orders and refunds become TallyPrime entries with GST split per line.
orders/paid and refunds/create become sales and credit note entries in TallyPrime through our Tally integration, with the GST split per line, ready for your accountant to review.
One stock count across website, marketplace and shop, with mismatches sent to a person.
When the same product sells on the website, a marketplace or in a physical shop, inventory_levels/update and the GraphQL Admin API keep one count. Disagreements go to a short list for a person rather than being overwritten.
Payloads carry only the customer fields each flow actually uses.
Subscriptions are declared in the app config or through the GraphQL Admin API, with include_fields and filters so payloads carry no more customer data than the flow uses. See about webhooks.
Every delivery's HMAC signature is checked, and mismatches are rejected.
Each delivery carries X-Shopify-Hmac-SHA256, a base64 HMAC SHA256 of the raw body keyed with the app's client secret. Mismatches are rejected. See verify deliveries.
Store the payload, answer at once, and do the work in a queue.
Shopify allows one second to connect and five for the whole request. We store the payload, answer at once and do the work in a queue.
Duplicates skipped by webhook id, plus a scheduled query for orders changed since the last run.
Duplicates are skipped by X-Shopify-Webhook-Id. Because Shopify does not promise that every delivery arrives, a scheduled job also queries orders changed since the last run, as Shopify recommends.
After 8 failed deliveries a subscription can be deleted, so we monitor and re-create it.
If Shopify gets errors, it retries 8 times over 4 hours. After 8 consecutive failures, a subscription created through the Admin API is deleted. We monitor for that and re-create it.
Names, addresses and contacts are requested field by field; unapproved fields arrive redacted.
Orders and customer events count as protected customer data. Names, addresses, emails and phone numbers must be requested field by field, and unapproved fields arrive redacted. See protected customer data.
Built on the GraphQL Admin API, since REST is legacy and new public apps need GraphQL.
Shopify marked the REST Admin API legacy on 1 October 2024 and new public apps must use GraphQL. We build on the GraphQL Admin API so the integration does not need a rewrite later.
New custom apps are made in Shopify's Dev Dashboard and approved by the store owner.
Since January 2026, new custom apps are created in Shopify's Dev Dashboard rather than in the store admin. The store owner, or staff with app development permission, approves it.
No. We build a custom app installed only on your store, owned by your Shopify account. We are not a Shopify partner listing apps for sale.
Yes. Paid orders and refunds are turned into TallyPrime vouchers with the GST split, and your accountant reviews them in Tally. See Tally integration.
The store owner's approval for a custom app with the scopes we list, access to your WhatsApp Business Account if WhatsApp is involved, and API keys for the payment gateway and courier, all in your company's name.
No. Webhooks fire after Shopify has recorded the event, and our handlers answer within Shopify's time limit and do the work afterwards.
The same patterns apply to any store with webhooks and an API. Ask us with the platform name.
Last updated