Bork CommerceMiddleware

Operations control room

Every commerce handoff,
in one place.

Connect ordering and commerce platforms to Domino, inspect incoming requests, and grow one reliable integration at a time.

SourceCommerce
RouteBork
TargetDomino
  • Live webhook streamSee WooCommerce requests arrive in real time.
  • Signature visibilityImmediately spot unsigned or invalid requests.
  • Built to expandAdd more commerce systems behind one Domino route.

Private operations workspace

Welcome back

Sign in to operations

Use your Bork account to continue.

Your session stays active in this browser for up to 14 days.

Operations

Live traffic

Not refreshed yet
Captured0retained webhooks
Signed0valid signatures
Attention0delivery warnings or errors
Worker OnlineWooCommerce → Domino active

Incoming

WooCommerce webhook stream

Up to 5 days of logs
Live · every 10 sec
Date / timeTopicMerchantStatus

No webhooks found

Adjust the filters or wait for a new request.

Select a webhook

Inspect the incoming payload and Domino processing without leaving the live overview.

Webhook inspector

Webhook

Incoming webhook
Domino order
Processing details

Configuration

Merchants

Connect each merchant's commerce platform to its own Domino Lite API configuration.

Connections

Configured merchants

0

No merchants configured yet.

Merchant setup

New merchant

01 Merchant
IN WooCommerce
OUT Domino Lite API

Server configuration

Connection details for this merchant's Domino Lite API.

Order remark

Product used to add the WooCommerce order remark to Domino.

Fallback products

Used when an article or addon has no valid numeric Domino number.

Delivery costs

Choose the VAT allocation, then configure only the product keys it needs.

Paymodes

Domino paymode key for each WooCommerce payment route.

Normal WooCommerce articles and addons still use their numeric SKU as Domino Nr. Only remark, fallback and delivery-cost products use Domino Key.

Access

Users & password

Change your own password and manage who can access this operations console.

Signed in as

—

—

Team

Console access

0

User account

Add colleague

Connection catalog

Commerce systems → Middleware → Domino

WooCommerce is the first source connector. The shared middleware model leaves room for additional commerce platforms without changing the Domino-facing contract.

Commerce source

WooCommerce

Capture active

Receives order webhooks and stores the original payload with topic, source, delivery identifiers, and signature status.

WooCommerceBork Middleware
Endpoint
/webhooks/woocommerce
Authentication
HMAC SHA-256 signature
Current phase
Capture and payload discovery
Operational target

Domino

Next phase

Each merchant stores its own Lite API URL, secret, remark and delivery-cost products, four paymode keys, and fallback product number behind one stable target adapter.

Bork MiddlewareDomino
Configuration
Available per merchant
Delivery adapter
Check, fallback, always deliver
Goal
Orders reach the kitchen, with visible warnings

Expandable by design

Next commerce connector

Future source adapters can normalize their events into the same internal commerce model before delivery to Domino.

Architecture

Bork Commerce Middleware

The commerce counterpart to Bork Booking Middleware, with a deliberately smaller first release.

01

Receive

Platform-specific adapters validate and capture commerce events.

02

Normalize

Provider payloads become a shared internal commerce event.

03

Deliver

A Domino adapter turns normalized events into POS requests.

27 August 2026

Team access and merchant routing

The console now supports individual colleague accounts, password changes and resets, active-access switches, and WooCommerce merchant identification through one shared signed webhook endpoint.