One screen to pay.One panel to ship.
Checkout on a single page: no account, company data from the GUS registry by tax ID, a pickup point and a payment method the customer knows. Then the order runs itself: status is computed from facts, label and invoice come out of the panel, the customer gets e-mail and SMS.
One page, no steps
The customer sees everything at once and pays once.
No “step 2 of 4”. Address, delivery, payment and summary on one screen, prices computed on the server, stock locked the moment the order is placed. The numbers on the screen match the list beside it.
The customer sees everything at once and pays once.
- No account
E-mail and phone are enough. We suggest an account after the purchase, not before. A logged-in customer has addresses and invoice profiles at hand.
- Tax ID, registry, VIES
Type the tax ID and company data comes from the GUS registry. EU companies are verified in VIES with a consultation number, so 0% intra-EU VAT is safe.
- Delivery with a point
Parcel locker, courier or pickup. Point finder for InPost, DPD Pickup and brokers, free delivery threshold, delivery date and time slot.
- A payment they know
BLIK and card, Przelewy24, PayU, Tpay, PayPal, Klarna, transfer, cash on delivery. Deferred payment and leasing for companies. Prices and totals are computed by the server.
- Coupon, gift card, points
Discount code, gift card and loyalty points in one field of the summary. Customers check the card balance themselves.
- Consents that are remembered
Terms with a version date, 18+ where required, marketing and cart reminder separately. Every consent stored with its legal basis.
- Comment and the rest
A message for the seller, a separate billing address, settlement currency and split into parcels if you enable it.
Status is computed from facts
Nobody clicks “shipped”. It is known.
Status is not a field to change by hand. It follows from what happened: a payment arrived, the parcel got a label, the carrier confirmed delivery. That is why an order cannot be “new” and “shipped” at once, and the customer sees the same state in their language, in the store and in e-mail.
Nobody clicks “shipped”. It is known.
- 010 s
New
order.placedStock reserved, e-mail to the customer and to you. An unpaid order expires on its own after the TTL.
- 020 s
Processing
payment_receivedThe gateway reports the payment, the status moves by itself. The customer gets a “paid” SMS. Packing list for the warehouse.
- 03now
Ready to ship
packedPacked. Label from the panel, one by one or as a ZIP for the whole shift. The invoice is issued at shipping.
- 04+2 h
Shipped
shipment.createdThe tracking number goes out by e-mail and SMS. The customer tracks the parcel on /sledzenie without logging in.
- 05+2 dni
Delivered
deliveredThe carrier webhook closes the journey. The return window starts today; the customer can download the invoice and return goods.
Order card
Everything about the order on one screen.
Order card 1042-004213 as it looks in the panel: no jumping between payment, shipping and invoice modules. Numbering is yours: your own pattern with prefix, date and counter.
Everything about the order on one screen.
- One card, the whole order
Customer, items, status stepper, actions. Hold with a reason, send back to packing, cancel with automatic stock return.
- Payment with facts
Who, how, how much and when. A refund, partial too, starts from the card and goes back to the gateway: Stripe, PayPal, Klarna, PayU, Przelewy24, Tpay.
- Label without leaving
The point from the cart is already on the order. Label one by one or a ZIP for the shift, split into parcels by weight, undo dispatch.
- Documents issue themselves
Invoice at shipping, pro forma and correction on request, packing list for the warehouse, KSeF with UPO receipt in the background.
- History that cannot get lost
Every event with time and source: gateway, carrier, operator, automation. What the customer sees and what you see.
- Two kinds of notes
The customer comment from checkout and internal notes. Kept apart so nothing leaks into an e-mail.
Store, Allegro, Amazon together
One list. Every channel.
Orders from the store and from marketplaces land on the same list, with the same status and the same card. Filters are arranged for work, not for a database.
One list. Every channel.
To fulfil, from today, awaiting transfer, only with issues, ERP held. Not “status = X” but “what do I do now”.
A salesperson enters the order in the panel, the customer gets a payment link. Off by default, one setting.
Allegro, Amazon, eBay, Erli, Kaufland, TikTok Shop and BaseLinker land on the same list with the same status.
The customer has a screen too
The customer knows what is happening before asking.
A “thank you” page with transfer details or a payment due date, public tracking without logging in, an account with history, downloadable invoice, reorder and return. E-mails at every change, SMS at the three that really matter to the buyer.
The customer knows what is happening before asking.
- 0 se-mailOrder placedwith number, summary and a payment link if not paid yet
- 0 se-mail · smsPayment receivedSMS “Order 1042-004213 paid”
- +17 mine-mail · smsShippedtracking number and a link to /sledzenie, no login
- +1 daye-mailReady for pickupfor in-store pickup instead of “shipped”
- +2 dayse-mailDeliveredthe return window starts today
- when needede-mail · smsCancelledwith information about the refund
After the sale without a spreadsheet
A refund goes the same way as the payment.
Returns and complaints have their own numbers, statuses and deadlines counted from delivery. Money goes back to the gateway without retyping an account number, and documents for the order are issued from what is already known.
A refund goes the same way as the payment.
- day 0Requestedfrom the account or a guest link, within the return window
- day 1Approveddecision in the panel, the customer gets an e-mail
- day 4Receivedthe parcel is back, items return to stock
- nowRefund in progressmoney moves in the gateway, the same way back
- day 5Refundedcase closed, invoice correction issued