E-commerce Engineering
This hub focuses on the engineering contracts behind commerce integrations: authenticated events, idempotent processing, inventory ownership, payment reconciliation and recoverable order workflows.
Which system owns inventory, price and order state?
How do checkout, payments and refunds reconcile safely?
DECISION FRAMEWORK
Define the boundary, then choose the technology.
Persist before processing
Verify the signature, store the event durably, acknowledge quickly and process asynchronously.
Name the source of truth
Choose explicit ownership for every field and reconcile drift instead of guessing.
Design for uncertain outcomes
Payment and shipping calls may succeed even when their response is lost.
CURATED GUIDES
All articles →Continue with practical guides.
Saudi commerce · Webhook operations
Salla webhook rotation: change endpoints without losing events
A production cutover plan for moving Salla webhooks between endpoints while preserving events, security, rollback and per-store subscription state.
Read the guideE-commerce engineering · ShopifyShopify bundles: design the cart transform contract
A production guide to fixed and customized Shopify bundles: composition, pricing, inventory, Cart Transform operations, failure policy and reconciliation.
Read the guideE-commerce engineering · ShopifyReliable Shopify webhooks: durable inbox and reconciliation
A production design for authenticating, deduplicating, ordering and recovering Shopify webhook-driven order and inventory synchronization.
Read the guideE-commerce engineering · SallaReliable Salla delivery promises: cutoffs, calendars and zones
A production design for turning Salla delivery-promise settings into versioned, testable checkout commitments without confusing them with carrier tracking.
Read the guideSaudi commerce · OAuth securitySalla OAuth refresh tokens: rotate once, recover safely
A production design for Salla OAuth token refresh that prevents concurrent reuse, stores each rotation atomically and handles uncertain network outcomes safely.
Read the guideSaudi technology · Post-quantum securityBuild a cryptographic inventory for Saudi post-quantum readiness
SAMA requires Saudi financial institutions to identify and classify cryptographic assets by Q4 2026. This is an engineering plan for doing it well.
Read the guideSaudi commerce · Product analyticsZid storefront analytics: build an event contract you can trust
Turn Zid storefront events into dependable product analytics with one versioned schema, idempotent delivery, identity stitching and order reconciliation.
Read the guideSaudi commerce · Catalog architectureSalla product variants: migrate the schema, not rows
Changing a Salla option can reshape every sellable variant. Use stable identity, shadow validation and reconciliation before writing prices or stock.
Read the guideSaudi commerce · AI integrationZid AI Agent Skill and MCP: a verified integration workflow
Zid provides an AI Agent Skill and an MCP server for its developer documentation. Here is how to turn them into a safe, testable integration workflow.
Read the guideSaudi commerce · Checkout policyTreat Salla customer groups as checkout policy
A practical architecture for using Salla customer groups to control payment, shipping and offer eligibility without turning segmentation into fragile manual configuration.
Read the guideSaudi commerce · API capacitySalla API limits: fair queues before more workers
Design per-store API budgets and fair queues for Salla integrations, with controlled retries, uncertain-write recovery and visible synchronization progress.
Read the guideSaudi commerce · Returns architectureZid reverse orders: separate return approval from refund execution
A practical architecture for Zid returns that separates approval, physical inspection, inventory decisions and refund execution while preventing duplicate financial actions.
Read the guide