Operating thread
Turn an order into one controlled shipment.
Address, package, available service response, postage, label, and tracking context form a deliberate fulfillment handoff.
- 01
Address
- 02
Rate
- 03
Postage
- 04
Label
- 05
History
See the real product
Start from the order your team is fulfilling.
Use genuine product captures to evaluate the operating record behind the claim.
Carry the order into complete shipping context.
Online Orders gives the team the customer, items, notes, and fulfillment branch that begin the handoff. On the configured shipping board, recipient, origin, end-shipper, package, and order details come together for address verification, rate comparison, postage, and label creation.
Compare responses from the configured service.
Available rate responses depend on the enabled shipping module, configured EasyPost and shipping-payment credentials, package data, origin and end-shipper settings, tenant markup, service responses, and rollout.
Verify payment before creating one label.
The merchant workflow verifies hosted postage payment before a single label is purchased. Creation depends on active credentials, funding, the selected service response, and the merchant's tested shipping setup.
Keep retrieval and tracking context visible.
A purchased label can be retrieved or reprinted from label history. Configured webhooks can update tracking state when the shipping service returns new events. The merchant surface described here is a single-label workflow.
Configuration and responsibility boundary
Start with the order; qualify the shipping service in setup.
Online Orders supplies the upstream order context. During scoped setup, we help validate address verification, available rate responses, hosted postage payment, single-label creation, retrieval, reprint, and tracking with the enabled module, configured shipping service and credentials, webhook setup, merchant settings, service responses, and rollout.
Inspect it
Qualify one shipment against the configured service.
Use the demo for product context, then confirm deployment-dependent behavior during a scoped rollout review.
- 01
Open Online Orders in a seeded store and inspect the order details that can precede fulfillment.
- 02
During a configuration review, confirm origin, end-shipper, package, markup, service, and credential settings.
- 03
Walk one test shipment through address verification and available rate comparison.
- 04
Verify hosted postage payment before creating a single label, then inspect retrieval and tracking history.
Workflow FAQ
Know what must be configured before the first label.
Does LiftedPOS create shipping labels?
The configured merchant shipping workflow supports single-label creation, retrieval, and reprint after address, service response, and hosted postage payment checks. Availability depends on the enabled module, credentials, settings, service response, and rollout.
Can an operator compare a shipping rate?
The shipping board can compare available rate responses returned by the configured shipping service. The result depends on address, package, merchant, credential, and service configuration.
What does the current Online Orders screenshot prove?
It proves upstream order context only. It is not presented as visual proof of address verification, rate shopping, postage purchase, label creation, or tracking.
How does tracking reach label history?
Configured webhooks can update tracking state when the shipping service returns an event. Webhook setup, credentials, service behavior, and rollout must be verified.
Public station terms
Know the price. Plan the way your team will use it.
Software is $100/month for the first station and $50/month for each additional station. A standard station is $499.99 to purchase or $39.99/month to lease. Cancel anytime with no long-term software contract. Leased equipment must be returned after cancellation or it is billed at the full purchase price. Payment terminals, processing, and separately scoped rollout work are separate from station pricing.