
Payments + Tillr Pay
Configured per merchantOnboarding, payment location, assigned reader, device readiness, and a successfully recorded test sale must be verified for the merchant's payment path.
Commerce infrastructure
Map payments, storefront, inventory, reporting, messaging, and hardware against the support matrix below. Verify the merchant's exact device, provider, and workflow before launch; a software path alone is not physical or provider-backed proof.

Commerce infrastructure
Review each payment, storefront, inventory, messaging, and hardware path against the merchant's actual setup before rollout.
How we integrate
Tillr publishes the readiness boundary, then validates the merchant's actual workflow during setup. Code-complete, configured, and physically verified are not the same state.
Operational modules
Each module covers a real workflow in your store. Status labels show what is available today and what we can connect during setup.

Onboarding, payment location, assigned reader, device readiness, and a successfully recorded test sale must be verified for the merchant's payment path.

Published storefronts can send browse, order, and pickup requests into Tillr's order workflow; channel setup and fulfillment still need merchant review.

Reviewed CSV/XLSX product imports, catalog tools, labels, and exports are available; third-party real-time catalog sync is not implied.

Transaction aggregation, operational dashboards, and export pipelines for real decisions.

Customer messaging lives in Tillr; provider-specific handoffs are validated before launch.

Supported scanners and printer paths still depend on the exact device, helper, connection, and workstation; payment terminals have separate readiness gates.
Compatibility matrix
“Available” describes a current product path, not automatic compatibility with every device. Physical-device proof is required before a configured path is treated as live for a merchant.
| Workflow or device | Support level | What to expect |
|---|---|---|
| Camera and keyboard-wedge barcode scanning | Available | Available in current iPhone/iPad checkout builds; Socket Mobile uses its configured feature path. |
| Receipt and label printing | Configured per merchant | Supported Star/Epson receipt paths and Zebra, DYMO, or OS label-print paths still require the matching printer, helper, connection, and workstation setup. |
| Printer-driven cash drawers | Configured per merchant | Drawer kick uses a connected supported receipt printer. Standalone USB drawers are not supported directly. |
| Customer email and SMS delivery | Configured per merchant | Tillr provides the workflow; provider, sender, consent, and delivery configuration must be validated for the merchant. |
| Tillr Pay readers and Tap to Pay | Configured per merchant | Software paths exist, but activation, merchant approval, location and reader assignment, signed-device requirements, and hands-on card-present validation still apply. |
How Tillr connects
Tillr centralizes operations and remains the source of truth. External systems plug into workflows — they do not replace your operating layer.

Channels connected
Online demand, back-office workflows, and store fulfillment stay tied to the same operational core.
Custom workflows
Most POS systems overpromise integrations or hide limitations. Tillr positions practical paths: migration help, export support, and custom bridges when your operation needs them.

Workflow support
Tillr can bridge the practical jobs around orders, inventory, accounting exports, and partner systems.