Connect stock events to an external system
Console: Settings → Webhooks. For the restaurant manager and authorised
integration owner. The feature requires stock access and permission to manage
stock settings. Webhooks send selected business events to another system;
confirm the destination, data purpose, business and owner before enabling one.
Create a subscription
- Select Create webhook and enter the destination's Endpoint URL. It
must be a public HTTPS receiver controlled by the authorised integration.
Local/private-network destinations, redirects and URLs containing credentials
are not supported. Do not enter a printer address or an unrelated service.
- Add a useful Description identifying the integration and owner.
- Choose the Events needed by that integration. The list covers stock low,
purchase-order creation/receipt, count submission, price change, item 86,
transfer creation and invoice upload. These are event notices, not a complete
data export or proof of downstream accounting.
- Set a Signing secret of at least 16 characters, or leave it blank for
TablePort to generate one. Use a secret dedicated to this integration.
- Select Create and verify the saved subscription and selected events.
- In Save your signing secret, store it in the integration's secret
manager, then use I've saved it. It is shown once; the list does not
reveal it again.
- Have the integration owner implement the
receiver contract and verify an agreed safe test event
before relying on the connection during service.
Do not place the secret in an endpoint URL, guest/staff notes, documentation,
chat prompts or screenshots. Signed means a signing secret is configured; it
does not prove the receiving system checks signatures or processes data.
Understand event outcomes
A saved or Active subscription does not prove an event reached the receiver.
Delivery happens separately from the restaurant action, and unsuccessful
attempts can be retried. The receiver must avoid processing repeated notices as
another order, stock movement or accounting entry.
A purchase-order-created event can concern a draft; it is not evidence the
supplier received an order. A count-submitted event is not approval of its stock
adjustment. An invoice-uploaded event is not invoice approval or stock receipt.
Verify each operational outcome through its normal TablePort workflow.
Pause or remove a connection
Disable changes the subscription to Inactive; Enable resumes it. These
save immediately, so coordinate with the integration owner and verify the
result. Pausing is not an undo of data already delivered or a guarantee that all
events during the pause will be replayed later.
Delete has a permanent confirmation and removes the subscription. Check the
actual endpoint and owner before confirming. Deletion does not remove copies
already held by the receiving system. The current page does not provide an
existing-subscription secret-reveal or delivery retry/log action; use the
supported integration/support path for those needs.
If events are missing or uncertain
If the integration owner is testing in staging, the current implementation
suppresses external webhook delivery. A saved subscription or completed internal
status does not prove an event arrived. Confirm the intended test environment
and ask the owner for receiver evidence; do not repeat a production restaurant
action to compensate for a staging test.
Check the selected business, Active status, selected events, correct public
HTTPS URL and receiver availability. Ask the integration owner to review its
signature checks, responses and saved processing result. Do not repeat the
restaurant action to manufacture another event or create a duplicate
subscription merely because delivery is uncertain.
If a secret was lost, preserve the original subscription and coordinate a
supported replacement with the integration owner. Do not disable signature
verification or use credentials from another business or company.
Escalate with business, subscription reference, event type, approximate time,
receiver result, relevant operation reference and exact error through authorised
channels. Exclude signing secrets, private network addresses, personal records
and raw sensitive payloads from public captures.