FACTORY ZERO

FZ-011 · INTEGRATIONS

PosPlugin

Sales data from point-of-sale systems through one API for app builders.

In development VALIDATION FZ stackPoint of sale
Visit posplug.in Launched: NOT YET
Status
In development
Pipeline stage
VALIDATION
Sector
INTEGRATIONS
Autonomy target
LEVEL 4 · SELF-OPTIMIZING
Built with
3 live · 2 planned

The problem

Every app that needs sales data builds and repairs a separate integration for each point-of-sale system.

What it does

PosPlugin is designed to connect each POS once and give your app its data through one API.

How it works

  1. Connect a merchant’s POS with a login or an API key; nothing is written to it
  2. AI maps its fields to one clean model, and a person confirms anything it is unsure of
  3. Your app reads orders, payments, menus and locations through one REST API and webhooks

A free sandbox for developers at launch; live pricing per connected location.

Connect a new merchant in half an hour instead of weeks of integration work.

TodayThe site and the early-access list are open. The connectors, the mapping engine and the API are being built.

The film

Any POS. One API.

Aims

Autonomous operation
Integration upkeep is the automation target. Connecting a merchant’s point-of-sale system is meant to be a guided half hour instead of a custom project, and keeping it connected is meant to need nobody: a monitor watches every sync for schema drift and failures, proposes the mapping fix, and tells ops what broke and why.
Intelligence
A model reads a POS’s API docs, specs or sample payloads and proposes how each field maps to one data model, with a confidence score on every field. It proposes and a person confirms: a low-confidence mapping never goes live on its own, and every decision is kept in an audit log. Moving the data is plain code.
Growth
Developer-led. A free sandbox with test POS data first, then pricing per connected location, set with the first customers. Restaurants are the first vertical. Growth is merchant locations connected, counted from the first customer that is not a pilot.
The technical detail

An integration layer for point-of-sale systems. It connects to a merchant’s POS with OAuth or an API key, pulls sample data read-only, and a model maps the POS’s fields to one data model (orders, payments, catalog items, locations) with a confidence score on every field; a person confirms the uncertain ones. Apps then read every merchant through one REST API and one webhook stream, with the original POS payload kept on each record, and write orders back where the POS allows. A monitor watches for schema drift and failing syncs. Card numbers never pass through it. The first vertical is restaurants. What exists today is the site at posplug.in and its early-access list; the connectors, the mapping engine, the unified API and the sandbox are designed and not yet written.

Related

From the same foundation.

All ventures