How do I receive the orders from my online store?
The orders that come in through your online store reach the ERP on their own and stay in an inbox, in Digital channels → Online store, Orders tab. From there each web order is converted into an ERP sales order, with its customer, its lines and its stock reservation. What can’t be converted stays in the inbox with the cause written down; it is never lost.
How do the orders reach the ERP?
The ERP asks the store for new orders every few minutes, on its own. Out of the box it is every 5 minutes. That interval is changed in the Orders (min) field of the Settings tab.
If you have set up the store’s notice, the ERP finds out sooner. The store notifies it as soon as an order comes in and the ERP brings the read forward. It isn’t required: without that notice, everything works the same, only with the wait of the normal cycle.
You can also bring them in right now. At the very top there is a bar with the store drop-down on the left and its two buttons on the right. Choose the store and click Fetch now. The ERP reads the pending orders and converts them there and then.
With All stores chosen, both buttons are greyed out: reading and converting are requested for a specific store. Hover over them and they tell you why. If you only have one store, it comes already chosen.
An order never comes in twice. Even if the ERP reads the same page again, each store order is saved only once.
What do I see in the Orders tab?
Under the work bar are the filters and, below them, the list: the order number in the store, the store it comes from, the date, the customer, the status and the total. If the order has already been converted, the last column has a button with the number of its document.
At the bottom of the list, the pager says how many orders meet the filter and which range you are in. It is the same list the rest of the ERP uses, so it works the same as the customer or item lists.
When you click a row, the panel on the right shows its detail: the identifier in the store, the payment gateway transaction if there is one, the conversion attempts and the document it generated.
How do I search for an order in the list?
Above the list there are two filters and a button to clear them.
The search box searches by number, by external identifier, by customer or by error cause. There is nothing to click: type and the list rebuilds itself as soon as you stop typing.
All statuses is a drop-down with tick boxes: tick the ones you want to see at the same time. It is what you need to work through the inbox, because what is waiting for a decision from you is two statuses —Outstanding and Error— and before you had to look at the list twice. With no box ticked, all of them are shown. The button tells you what you are seeing: with one or two, their names; from three on, how many.
Clear filters clears the search box and the tick boxes in one go. It is greyed out when there is nothing to clear.
The store isn’t here: it is the one in the top bar, and it applies to the whole tab —the list and the two runs—.
The search box has a limitation with accents. The buyer’s name is searched inside the text exactly as the store sent it, and some platforms write accents in a way that doesn’t match. If you search for Lucía and it doesn’t appear, try a part without accents, such as Luc.
How do I convert an order into a sales order?
Select the order in the list and click Convert to sales order, in the panel on the right. The ERP creates the document and tells you its number.
To do it with all of them at once, choose the store and click Convert pending, in the top bar. The button shows in brackets how many it is going to convert, and it is greyed out when there are none. It converts all of that store’s orders with Outstanding status. When it finishes it tells you how many went through and how many failed. An order that fails doesn’t stop the others.
Normally you won’t have to click anything. Orders are converted on their own as soon as they come in: reading and converting are the same job. The buttons are there for when something failed and you have already fixed it.
Converting the same order twice doesn’t create two documents. If the order already had one, the ERP reuses it and warns you: ‘That order already had a document: it has been reused.’
What exactly does the conversion create?
It creates an ERP sales order, with everything that implies: numbering, lines, tax calculation and reservation of the corresponding stock. It is created in one go, complete: if something fails along the way, no half-made document is left.
The customer comes from the order itself. The ERP first looks for a customer with that Tax ID, then for one with that email address and, if it doesn’t find any, it creates the record. Customers created this way have a code that starts with WEB.
The order lines become document lines. The item is looked up by SKU, by barcode and by reference, in that order.
Shipping goes in as a separate line, with the description Shipping. A coupon discount goes in as a negative line, with the description Coupon discount and the coupon code after it. If the discount has no coupon, the line says Online store discount. That way the document shows the same as what the customer saw when paying and the figures add up.
The document has the store order number in its reference, and a note saying which store it comes from, with which external identifier and with which payment method. If the buyer wrote something when placing the order («leave it at the door», «it's a gift»), the note ends with Nota del cliente: and what they wrote. In WooCommerce and Shopify; not yet in PrestaShop.
After creating the document, the ERP tries to let the store know that the order is processing. That notice is a courtesy: if it fails, the document isn’t undone, the failure is just recorded.
In WooCommerce, «processing» means the order is paid: WooCommerce sets a payment date and sends the buyer the «Processing your order» email. So if the order is still waiting for payment (a bank transfer, cash on delivery or a cheque: «Pending payment» or «On hold»), the ERP leaves it as it is. When you confirm the payment in the store and move it to Processing, the ERP records the payment in the next sync.
What happens if an item in the order isn’t recognised?
The whole order is left with Error status and no document is created. A document is never created with fewer lines than the customer bought.
The cause is saved and shown in the order detail, with the key that wasn’t recognised and the line description. For example: ‘Unknown SKU “CAM-ROJ-XL” (line “Red shirt size XL”)’. If there are several lines, they all appear.
To fix it, go to the item record in the ERP and give it the SKU, barcode or reference the store identifies it by. Then go back to the order and click Retry the conversion.
This is the most common reason for an order in error, and it nearly always means the same thing: an item that is sold on the website and doesn’t have its SKU set in the ERP.
What happens if the total doesn’t add up?
The ERP calculates the document total before creating it and compares it with what the store says it has charged. If the difference is more than one cent, it doesn’t create anything and the order is left in Error.
The message gives both amounts: ‘The calculated total (121,00 EUR) does not match the amount charged by the store (119,50); difference 1,50. The document has not been created.’
It is a deliberate safeguard. The amount the customer paid is the right one, and a document that doesn’t match the payment causes a bigger problem than a stopped order. It usually comes from a different VAT rate in the store and in the ERP, or from rounding that the platform does differently.
To resolve it, make the criterion the same in the ERP and click Retry the conversion. If the mismatch is a one-off and you prefer to enter it by hand, discard the order with a reason and create the document yourself.
How do I retry an order that failed?
Select the order in Error and click Retry the conversion. The ERP clears the previous cause and tries again from scratch.
Retry after fixing what was failing, not before. If the cause is still there, it will fail again with the same message. The number of times it has been tried is shown in the detail, in Attempts.
Only orders in Error are retried. An outstanding order is converted with Convert to sales order, and one already converted isn’t touched.
How do I discard an order?
Type the reason in Reason for discarding and click Discard. The reason is required: it is the only thing that will explain in six months’ time why that order has no document.
Outstanding orders and those in error can be discarded. It is useful for tests, for orders cancelled in the store or for those you decide to enter some other way.
An order that has already been converted can’t be discarded. A document already exists, and what you have to do is void that document through the ERP’s normal channels.
Discarding doesn’t delete anything. The order stays in the list with Dismissed status and its reason in view, and it can be looked up whenever needed.
What happens if the order changes in the store?
It depends on what you have done with it. If the order is still Outstanding, the ERP refreshes what it has with the latest the store says. There is nothing of yours to spoil yet.
If you have already converted or discarded it, the ERP doesn’t touch it. From that moment the truth is the ERP document, or your decision to discard it. A later change in the store is handled on the document, like any other change.
If the store refunds part of an order that is already a sales order but isn’t invoiced yet, its panel warns you (‘The store refunded … of this order’) and offers the Refund … from the advance button. It is explained in What do I do if the store refunds only part of an order that isn’t invoiced?.
What happens if the store cancels an order?
The order changes to Cancelled in the store, in red, and its record shows a notice. It shows up on the next order read from Shopify or WooCommerce. Not in PrestaShop: there each store names its own statuses, and the ERP doesn’t know which one is “cancelled”.
- If you hadn’t converted it yet, it is no longer converted.
- If it was already a sales order, the ERP doesn’t undo it by itself, because that moves stock and receipts. Its record shows a button with what needs doing, and you click it:
- Cancel the sales order, if it isn’t invoiced yet. It is cancelled there and then, and the reservation and the receipts are reversed. If it already has a delivery note, the ERP asks you to cancel the delivery note first.
- Make the corrective invoice, if it is already invoiced (for example, because receipts are invoiced on payment). An issued invoice isn’t cancelled: it is corrected. The ERP creates the corrective invoice for the whole invoice as a draft and opens it for you. Review it —if the store refunded only part, remove what isn’t refunded— and issue it.
- Open the corrective invoice, if you had already created it. Another one isn’t made: the existing one opens.
- Refund the advance, if the sales order is already cancelled but the payment was kept as an advance (receipts with the order). Cancelling the order doesn’t touch its advance; this button refunds its whole balance through the account it was collected in, and the store’s return is recorded.
The notice in the record tells you where things stand: if the corrective invoice is a draft, it asks you to issue it. Once it is issued, or the sales order is cancelled, the button goes away and the notice says so. When you issue the corrective invoice, the return the store sent is recorded in Receipts.
Does the store find out when I ship an order?
Yes. When the sales order of an online order has its delivery note, the next sync tells the store that it is shipped. In Shopify the order is fulfilled and the buyer gets the shipping email; in WooCommerce and PrestaShop it moves to the status the store has for “shipped”. Each order is notified only once.
What counts is the delivery note. A draft or cancelled delivery note doesn’t count.
If receipts are recorded on payment, the order is invoiced when paid and there is no delivery note. That invoice doesn’t notify by itself, because being paid doesn’t mean the parcel has left. It notifies when you type its Tracking number (on the next sync) or, straight away, with the order’s Notify shipment button.
If the store doesn’t get the notice, the reason is shown and it is tried again on the next sync.
How do I ship an online order and notify the buyer in one go?
With Ship and notify, in the order panel of the Orders tab. It shows on converted orders that still have something left to ship.
- Select the order in the list.
- Check the Carrier. It comes proposed: the one on the customer’s record or, if there is none, the one from that store’s last shipment. Change it with the magnifying glass if needed.
- Type the Tracking number the carrier gave you. It is optional.
- Press Ship and notify.
The ERP makes the delivery note with everything the order has left, with the carrier and the number, confirms it (stock leaves the warehouse as with any delivery note) and notifies the store at that moment, without waiting for the sync. If the store doesn’t answer, the delivery note stays made and the notice is retried on the next sync.
The button ships the whole order. To ship only part of it, make the delivery note by hand from the sales order.
If the order was already invoiced on payment, there is nothing left to ship and the button is called Notify shipment. It works the same, but makes no delivery note: it puts the carrier and the number on its invoice and notifies the store.
How does the buyer get the tracking number?
With Ship and notify it is typed when shipping. If you make the delivery note by hand, type it on the delivery note, in Tracking number, next to the Carrier, on the delivery addresses card (Other details tab). The shipping notice carries the number and the carrier’s name:
- In Shopify, the buyer gets them in the shipping email. If Shopify knows the carrier (Correos, SEUR, MRW, GLS…), the email also has the link to track the parcel.
- In WooCommerce and PrestaShop the number travels; the carrier has nowhere to go.
Type it before confirming the delivery note. The notice goes out on the next sync and only once: a number typed afterwards no longer reaches the store. If you miss it, add it by hand to the order in the store.
Without a number, the notice goes out anyway, just without tracking.
If something goes wrong
| What you see | What has happened | What to do |
|---|---|---|
| ‘Unknown SKU “…” (line “…”)’ | No ERP item has that key | Put the SKU, barcode or reference on the item record and click Retry the conversion |
| ‘The calculated total (…) does not match the amount charged by the store (…); difference …. The document has not been created.’ | The ERP amount and the store amount don’t match | Check the item’s VAT; correct it and retry |
| ‘The order has no buyer Tax ID or email: the customer cannot be identified.’ | The order arrived without details to recognise the buyer | Enter the order by hand and discard the web order with that reason |
| ‘The order has no lines.’ | The order arrived empty | Check it in the store; if it is a test, discard it |
| ‘Unreadable payload: …’ | The order arrived in a format the ERP doesn’t understand | Tell support, giving the order number |
| ‘There is no order parser for platform ….’ | That platform has no order reading in the ERP | Check with whoever is implementing the ERP |
| ‘Could not issue the sales order: …’ | The document couldn’t be created | Read the reason at the end of the message; it is usually a detail missing on the customer or in the warehouse |
| ‘Order … has an error (…); use Retry to reprocess it.’ | Convert has been clicked on an order in error | Use Retry the conversion |
| ‘Order … is discarded (…).’ | Convert has been clicked on a discarded order | A discarded order isn’t converted; enter it by hand if needed |
| ‘Only an order with an error can be retried (current status: …).’ | Retry has been clicked on an order that isn’t in error | Use Convert to sales order |
| ‘An order that has already been converted cannot be discarded (void the document if appropriate).’ | You are trying to discard something that already has a document | Void the document from invoicing |
| ‘Enter the reason for discarding the order.’ | The Reason for discarding field is empty | Type the reason and click Discard again |
| ‘Select a store: ingestion is requested for a specific store.’ | All stores is chosen | Choose a store in the drop-down at the top and click Fetch now |
| ‘Select a store: converting pending orders is one run per store.’ | All stores is chosen | Choose a store in the drop-down at the top and click Convert pending |
| ‘A sync is already in progress for this store. Wait for it to finish.’ | Another read or publication is working on that store | Wait a few minutes and try again |
| ‘You do not have permission to manage the online store orders.’ | The edit permission is missing | Ask whoever administers the ERP for it |
| ‘You do not have permission to view the online store orders.’ | The view permission is missing | Ask for access to the online store module |
| ‘Order … was converted, but the store did not receive the “processing” status: …’ | The document was created, but the notice back to the store failed | There is nothing to redo; change the status in the store by hand if you need to |
| ‘That order already had a document: it has been reused.’ | The order was already converted | It isn’t an error; click Open the document to see it |
| ‘The store has cancelled this order. Its sales order is still open…’ | The buyer or the store cancelled it after it was converted | Click the button in its record: Cancel the sales order, Make the corrective invoice, Open the corrective invoice or Refund the advance, depending on where things stand |
| ‘Order … has been shipped, but the store did not receive the shipping notice: …’ | The store rejected or didn’t answer the notice | Read the reason; it is retried automatically on the next sync |
| No new orders arrive | The store is deactivated, not adopted, or the keys aren’t valid | Check the Settings tab and click Test connection |
See also: The customers who buy on the website · Connect my online store · Keep stock and prices up to date · The store receipts
More about Online shop
- How do I view and prepare my online store’s receipts?
- How do I show colours and materials with a photo instead of their name?
- How do I connect my online store to the ERP?
- How do I link a store that already has products?
- Selling online with the ERP behind you
- Who are the customers who buy on the website?
- How do I keep stock and prices up to date in the store?
- How do I prepare my online store’s catalogue?