Manage orders and fulfilment
See what a customer bought, review their payment attempts, and keep track of what still needs to be delivered.
On this page
An order brings the purchase together
Open Orders for the purchase itself: the items, customer, total, addresses, payment attempts and fulfilment. Use Payments when you need the evidence for one particular attempt to pay.
One order can have several payment attempts. A retry does not always mean a second purchase, and one customer can have many orders. Always match the order and payment before delivering.
- CustomerAlex Morgan
Their history can include many orders.
alex@example.com - Order #1001Design consultation
One purchase, with its own total and fulfilment record.
$49.00 USD - Payment attemptsOne retry, one purchase
An order can be paid after an earlier attempt expires.
Attempt 1: Expired · Attempt 2: Paid
Fulfil the order once. Read each payment attempt if something needs your decision.
Orders come from checkouts, invoices, your connected store and the Checkout API. Stores and the API can send item details, shipping, tax, discounts and addresses. A checkout creates an order for its product or plan. A payment toward an invoice creates an order with the invoice's lines when it pays the whole invoice, or one line such as "Payment toward INV-0042" when it pays part of it. Missing details mean the source did not provide them; Railbed does not invent an address or a product.
Everyone on your team can read orders. Owners and managers can mark them fulfilled and export them.
Find the orders that need you
- Check Test or Live mode. Orders, customers and payments are separate in each mode.
- Choose a view at the top of Orders. To see one source only, choose it in All sources: WooCommerce, Checkouts, Invoices or Checkout API.
- Search for an order number, a customer's name or email, a product or SKU, your reference, or an order or payment ID. Clear filters returns to the full list when nothing matches.
- Open a row to review the order. Show more loads the next results.
| View | What it includes |
|---|---|
| All | Every order that matches your source and search |
| Not fulfilled | Paid orders waiting to be shipped or delivered |
| Needs your decision | Orders whose payment arrived but didn't pass a check. Team members who can't accept payments see Needs a decision |
| Awaiting payment | Orders whose payment is Open or In progress |
| Ended unpaid | Orders that ended Declined, Expired or Canceled |
The counts on Not fulfilled and Needs your decision stop at 100+: a capped count, not exactly 100. The total beside the page title can read 10,000+ the same way.
Filters stay in the page address, so refreshing or using Back keeps your view. Someone opening a link to an order still needs to sign in to the same business and mode.
Read an order
The order opens in a panel over the list, so you keep your place. Use Previous order and Next order, or K and J when the panel has focus and you aren't typing in a field.
- Customer: their name, contact and what they have paid so far. Open it for their customer page.
- Items: products, quantities, variants and SKUs, with the subtotal, discount, shipping and tax when the source sent them. The total is what the customer was charged, in the order's currency.
- Ship to or Bill to: the address as supplied, with a button to copy it. Addresses are not checked against a postal service.
- Payment: the card provider (or the coin and network for a crypto payment), Received and when it was paid. With more than one attempt, each is listed newest first with its own status. One failed or expired attempt does not undo another that is Paid.
- Timeline: the order's and its payments' events in order.
- Answers: what the buyer typed for the questions your checkout or invoice asked (Ask buyers for their details).
- Details: the order ID to copy, the store's own order number and store name for a store order, and Your reference when one was sent.
Received is the net amount that reached your wallet, in dollars, after fees. It is a different figure from the order total, and reads Not reported yet until it is reported. See wallet and settlement.
When Railbed support has corrected a detail of this order or its customer for you, the panel shows Corrected by Railbed support with View original values. A correction never changes the order's amounts or payment evidence; see Customers.
Warnings at the top of an order
| Warning | What to do |
|---|---|
| A payment didn't pass a check | Choose Open payment and follow Payments that need your decision. Don't fulfil until it is Paid |
| Only part of the total was paid, or it was paid in another currency | Choose Open payment, then check with the buyer before you fulfil |
| The buyer paid twice (or more) for this order | Check each payment under Payment. Deliver the order once, then agree any refund for the extra payment with the buyer |
Marking an order fulfilled never refunds a payment. Railbed doesn't move money back to buyers.
Payment and fulfilment are separate
A payment status answers whether the order was paid. Fulfilment records whether you have delivered it. Mark as fulfilled cannot turn an unpaid order into a paid one and does not send money.
| Fulfilment label | Meaning |
|---|---|
| No shipping | A paid order created without a shipping requirement, such as a service or digital product |
| Not fulfilled | A paid order waiting to be shipped or delivered |
| Fulfilled | You or the connected store recorded delivery or dispatch |
An unpaid order shows no fulfilment label. No shipping is not proof that a digital item was delivered; your business or connected system still handles delivery. A fulfilment label alone is not proof of payment either.
Mark an order fulfilled
For an order managed in Railbed:
- Open the order and confirm it reads Paid. Check the items, customer and delivery details.
- Deliver the goods or service through your normal process.
- Choose Mark as fulfilled. To correct the record later, choose Mark as not fulfilled.
To mark several at once, tick their rows and choose Mark as fulfilled in the bar that appears. Shift-click ticks every row between two ticks, and Escape clears the selection. You can select up to 100 orders. Railbed checks each one: unpaid orders and orders whose fulfilment comes from a store are skipped, and the message says how many were marked and how many were left.
If an order reads Needs your decision or Not received, choose Open payment and follow Payments that need your decision. Don't mark it fulfilled before its payment is Paid.
Export orders
Choose Export CSV to download the orders that match the current view, source and search. To export only some orders, tick them and choose Export CSV in the selection bar.
The file has the order number, date, status, fulfilment, customer and contact, items and units, currency, subtotal, discount, shipping, tax and total, Received (net, USD), source, store and store order, your reference, both addresses, the buyer's Answers, and the order and payment IDs.
- An export holds up to 10,000 orders. When more match, the dashboard says Export limited to 10,000 rows; narrow the filter and the file ends with a row saying the same, so a cut-off file is never mistaken for a complete one.
- Keep the currency with every amount; don't add USD, EUR and other currencies together. Received (net, USD) is a separate measure: what reached your wallet, in dollars, after fees, whatever coin it arrived in.
- Exports contain customer details. Keep the file only where you mean to keep those details. Deleting a customer's data in Railbed does not reach a file you already downloaded.
When something looks wrong
| What you see | What to check |
|---|---|
| An order is missing | Confirm the mode, clear filters and search by its order or payment ID. An order from the other mode says to switch modes |
| A customer tried again | Look under Payment; several attempts can belong to the same order |
| An expired order later becomes Paid | A late payment can still settle and update the order. Read its current status before you send a new request |
| Fulfilment can't be changed here | The order isn't paid yet, its fulfilment comes from a store, or your role can't change orders |
| The timeline says Canceled in your store or Refund recorded in your store | The store reported it. The payment stays as it is, and Railbed didn't move any money; refund the buyer yourself if money arrived |
| The store shows a different fulfilment state | Check the integration, then make the change in the store |
| An address or item is missing | Check what the store, invoice or API sent when the order was created |