Skip to main content
Connecting your POS to storekit eliminates double-handling and keeps your systems in sync. Orders placed online flow directly to your existing kitchen workflow, and menu changes in your POS can automatically update your online menu.

​
Why Connect a POS?

Without a POS integration, you’re managing two separate systems:
  • Manually entering online orders into your POS
  • Updating menus in multiple places
  • Reconciling sales across platforms
With a POS integration:
  • Orders inject directly into your POS and kitchen printers
  • Menus stay synchronised between systems
  • Inventory updates reflect across platforms
  • Discounts and loyalty from your POS apply to online orders

​
Integration Types

Different POS systems integrate in different ways. Understanding these types helps you know what to expect.

​
Push Integrations

The POS or menu platform automatically sends data to storekit whenever changes are made.
IntegrationHow It Works
DeliverectPublishes menu changes to storekit automatically
StreamPushes menu updates when published
Pros: Fastest sync, no manual intervention needed
Cons: Requires the source system to support push

​
Pull Integrations

storekit fetches data from your POS on demand or on a schedule.
IntegrationHow It Works
Zonal (Aztec)Pulls menu on demand or scheduled
Lightspeed K-SeriesPulls menu on demand or scheduled
SyrvePulls menu on demand
PointOnePulls menu on demand
Pros: Works with most enterprise POS systems
Cons: Changes aren’t instant; requires sync trigger

​
Manual Linking

Products are created in storekit and linked to your POS using product IDs (PLUs).
IntegrationHow It Works
TISSLProducts linked via PLU codes
ComtrexProducts linked via product ID
CentegraProducts linked via product ID
Pros: Full control over online menu design
Cons: More setup work; manual updates needed

​
Feature Comparison

Not all integrations support every feature. Here’s what each offers:
IntegrationMenu SyncOrder InjectionPay at Table
Lightspeed K-Series✓ Automatic✓✓
PointOne✓ Automatic✓✓
Zonal✓ Automatic✓-
CentegraManual✓-
TISSLManual✓✓

​
How Orders Flow to Your POS

When a customer places an order on storekit: 
Customer places order
        ↓
Payment processed
        ↓
Order sent to storekit backend
        ↓
Order injected to POS
        ↓
POS sends to kitchen printer/KDS
        ↓
Order confirmation returned
The entire flow typically takes 2-5 seconds. If the POS is temporarily unreachable, storekit queues the order and retries automatically.
Orders always complete for the customer even if POS injection is delayed. You’ll see the order in your storekit dashboard and can manually enter it if needed.
If an order fails to sync to your POS, you’ll receive an email notification with the error details and a direct link to the order. This ensures you never miss an order that needs manual attention, even if the customer has already paid online.

​
Choosing the Right Approach

​
Use Push Integration If:

  • You already use Deliverect or Stream for aggregator management
  • You want fully automated menu sync
  • Your menu changes frequently

​
Use Pull Integration If:

  • You have an enterprise POS (Zonal, Lightspeed)
  • You want scheduled sync at specific times
  • You need tight inventory integration

​
Use Manual Linking If:

  • Your POS doesn’t support API-based menu sync
  • You want complete control over online menu presentation
  • You have a simple, stable menu

​
Getting Started

Lightspeed K-Series

Full menu sync, order injection, and pay at table

PointOne

Full menu sync, order injection, and pay at table

Zonal

Full menu sync with basket validation

Centegra

Manual product linking with floor plan sync

TISSL

Manual product linking with pay at table

​
Need a Different POS?

We’re always evaluating new integrations. If your POS isn’t listed:
  1. Check if your POS works with Deliverect or Stream (middleware options)
  2. Submit a feature request with your POS details
  3. Use our Webhooks to build a custom integration
When requesting a new integration, include your POS name, version, and how many venues would use it. High-demand integrations get prioritised.