Issue an integration key without exposing it forever
Authorized staff can create and revoke online-order API keys. A new secret is returned once so an integration can store it securely, while the administrative record can later identify and revoke the credential. The API is rate-limited to protect the order channel from uncontrolled traffic.
Let the server decide the sellable order
The server resolves products and authoritative prices, then calculates discounts and tax rather than accepting client-provided totals as truth. Inventory is reserved or the order fails, and duplicate external order identifiers are rejected so a storefront retry does not quietly create a second order.
Use deliberate order states
Online orders can move through pending, confirmed, preparing, ready, completed, and cancelled states using allowed transitions. The operations page can filter by channel and poll for new work, with an audible cue for a new order, so staff can manage progress without losing the external identity.
Connect accepted orders to fulfillment
When the restaurant workflow is configured, accepted orders can enter the kitchen flow with the source and line-item context required by preparation. LiftedPOS is describing an online-order API and management workflow—not promising a universal, turnkey hosted consumer storefront for every merchant.
Use the actual workflow, inspect the resulting record, and ask how the behavior is configured for your locations. Availability can depend on enabled modules, hardware, and payment setup.
Move from the feature to the operation
LiftedPOS is designed so this capability does not sit alone. It shares customer, employee, product, location, transaction, and reporting context with the rest of the system. That is the difference between checking a feature box and removing a handoff from the day.