An integration layer for point-of-sale systems. PosPlugin connects to a merchant's POS, uses AI to map its fields to one clean data model, and serves that data through one REST API plus webhooks.

How long does connecting a POS take?

On POS that PosPlugin supports, the setup is designed to take under 30 minutes in six steps: pick the POS, connect with OAuth or an API key, discover sample data read-only, review the AI mapping, run a test order, and go live.

Does PosPlugin store card data?

PosPlugin is designed never to receive full card numbers: only card brand and last four digits as the POS returns them, to stay out of PCI card-data scope.

Can I use PosPlugin today?

PosPlugin is in early access. Join the list at posplug.in and say which POS systems you need; access opens in waves, starting with restaurants.

PP-01 / AI integration layer Status: early access Vertical 01: restaurants

Any POS. One API. Live in30minutes.

PosPlugin's AI maps any point-of-sale system to one clean data model, so your team connects new merchants in minutes, not months.

Get early access Watch the film · 47 s See it connect

Patch board · live

Event busLive

order.created12:04:11

"id": "ord_k3v9qa"

"location_id": "loc_8f2k"

"total": 2963

"pos": "tablet_pos_b"

payment.captured12:04:09

"id": "pay_7mz2te"

"method": "card"

"amount": 2963

"pos": "cloud_pos_a"

item.updated12:04:07

"id": "itm_q81xrw"

"name": "Smash burger"

"price": 1250

"pos": "kiosk_pos_c"

order.updated12:04:05

"id": "ord_b20jfd"

"location_id": "loc_8f2k"

"total": 4180

"pos": "legacy_pos_d"

[ 00 ] The film

Any POS. One API. 47 seconds.

Early access · illustrative sample data

[ 01 ] The problem

POS integrations are a tax on every roadmap.

ERR-01

Hundreds of POS systems

api_count: too_many

ERR-02

Every one a custom integration

effort: from_scratch

ERR-03

Weeks of work that breaks when the vendor changes an API

last_break: yesterday

PosPlugin cuts through.

One layer. Every POS. Patched.

[ 02 ] The 30-minute connection · target, supported POS

Six steps. One clock.

Scroll to run the setup ↓

ElapsedBudget 30:00

00:00

00target 27:00 · buffer 3:00

Step 01 · 1 min budget

Pick POS

Search the list, or just type its name.

Clock stopped · connection live

3 minutes to spare.

setup.posplug.in

> search pos:cloud

[■] Cloud POS AKNOWN MAPPINGS

[ ] Cloud POS BSUPPORTED

[ ] Cloud Kiosk CSUPPORTED

Coming: can't find it? Upload its API docs, get a draft connector.

POS·APOSPLUG

[✓] Read orders and payments [✓] Read menu and locations [✓] Create orders (where the POS allows)

Authorize with OAuthor paste an API key

> PULLING SAMPLE DATA · READ-ONLY

locations12

menu + catalog486 items

recent orders2,140

payments2,098

Nothing is written to your POS during discovery.

POS FIELDUNIFIEDCONF

ticket_total42.10order.total98% AUTO

tkt_open_ts1727093051order.created_at97% AUTO

pmt_type_cd2payment.method71% CONFIRM

itm_desc"Smash burger"catalog_item.name99% AUTO

svc_chg3.00order.tips64% CONFIRM

AI>'ticket_total' looks like the order total including tax.

POSPOSPLUGYOUR APP

> TEST ORDER ord_test_7Q2 · €29.63

location[PASS]

catalog_items[PASS]

order[PASS]

payment[PASS]

webhook[200 OK]

Live

12 locations syncinghealth monitoring: on

[ 03 ] How it works

Three layers. Zero glue code.

Hover or tap a unit to open it.

IN POS·APOS·BPOS·C+ new POS

RU-01

Connector layer

OAuth, API keys and partner credentials
Polling or webhooks, with retries and rate limits
Templates for REST, GraphQL and file exports

RU-02

AI mapping engine

Reads API docs, specs or sample payloads
Confidence score on every field
Every confirmed mapping trains the next one

RU-03

Unified API + webhooks

One REST API, one event stream
Original POS payload kept on every record
Two-way where the POS allows: inject orders

HM · ALWAYS ON

Health monitoring

Detects schema drift and failing syncs
Suggests a mapping fix before customers notice
Alerts ops with what broke and why

OUT Loyalty appDelivery platformAccounting / BI

[ 04 ] For developers

Write it once. Works with every POS.

1curl "https://api.posplug.in/v1/orders?location_id=loc_8f2k" \
2  -H "Authorization: Bearer $POSPLUG_KEY"

1const res = await fetch(
2  "https://api.posplug.in/v1/orders?location_id=loc_8f2k",
3  { headers: { Authorization: `Bearer ${process.env.POSPLUG_KEY}` } }
4);
5const { data } = await res.json();

1import os, requests
2
3res = requests.get(
4    "https://api.posplug.in/v1/orders",
5    params={"location_id": "loc_8f2k"},
6    headers={"Authorization": f"Bearer {os.environ['POSPLUG_KEY']}"},
7)
8orders = res.json()["data"]

Same call. Same shape. Whichever POS is behind it.

200 OK · application/json48 ms

{
  "data": [
    {
      "id": "ord_01J9ZK4",
      "location_id": "loc_8f2k",
      "channel": "dine_in",
      "status": "completed",
      "line_items": [
        {
          "name": "Smash burger",
          "qty": 2,
          "unit_price": 1250
        }
      ],
      "tax": 213,
      "tip": 300,
      "total": 2963,
      "currency": "EUR",
      "pos": {
        "type": "cloud_pos_a",
        "ref": "T-88213"
      },
      "created_at": "2026-09-23T12:04:11Z"
    }
  ],
  "has_more": false
}

webhooks → your.app/hooksLIVE

12:04:11order.created · loc_8f2k200

12:04:09payment.captured · loc_3m1q200

12:04:06item.updated · loc_9xa7200

12:04:02order.updated · loc_1p0d200

12:03:58location.synced · loc_8f2k200

12:03:55order.created · loc_3m1q200

[ 05 ] Who it's for

Built for people who need POS data at scale.

UNIT 01PRIMARY

SaaS vendors

PAIN: One integration per POS. Forever.
FIX: One API that covers every merchant's POS.

UNIT 02OPERATORS

Multi-location operators

PAIN: Different POS per site. No single view.
FIX: Unified data. No hardware swap.

UNIT 03PARTNERS

POS resellers & implementers

PAIN: Slow go-lives. Endless tickets.
FIX: Merchants on third-party apps the same day.

[ 06 ] Why PosPlugin

Spec sheet.

PosPlugin compared with building in-house, unified POS APIs and delivery hubs. PosPlugin column: design targets, not yet measured.
PARAMETER	PosPlugin	Build in-house	Unified POS APIs	Delivery hubs
Time to connect	Target: under 30 minutes on supported POS	Weeks to months per POS	Minutes, once the POS is on their list	Days
POS coverage	Supported POS, plus AI-drafted connectors for any POS with a documented API	Only what you build	A fixed list, often 80–140+ POS	POS their partners support
Full data: catalog, payments, locations	Yes, where the POS exposes it	If you build it	Varies	Orders and menus
Non-developer setup	Yes, guided	No	Varies	Partly
AI mapping with confidence review	Yes, every field	No	Not advertised	Not advertised

> PosPlugin is in early access: its column is what we are building to, not a measurement. Other columns from their public docs, September 2026.

[ 07 ] Trust & security

Boring about security. On purpose.

> Designed in from the first line of code. PosPlugin is in early access, so none of this is audited yet.

No card numbers

We never receive full card numbers, only brand and last four as the POS returns them. Designed to stay out of PCI card-data scope.

Encrypted everywhere

In transit and at rest. POS credentials live in a secrets vault.

Per-tenant isolation

Your merchants' data never mixes with anyone else's.

Full audit log

Who changed which mapping, and when. Every AI decision too.

Built for GDPR

Data export, deletion and regional storage options, with a DPA that lists every sub-processor.

> AI proposes. Humans confirm. Low-confidence mappings never go live alone.

[ 08 ] Pricing

Free sandbox for developers. Simple per-location pricing when you go live.

MODE A · SANDBOX

Free

Test POS data, the full API and webhooks. Build before you buy.

MODE B · LIVE

Per location

Pay for connected locations. Prices set with our early customers.

Join the early access list

Plug in.
Go live.

Early access opens in waves. Tell us which POS systems you need.

Rather write it yourself? [email protected]