The Monitor shows every Shopify order with the status of its documents in inFakt, in real time. If a document wasn't created, you see it here, see why, and fix it without leaving Shopify.
Search by order ID
Type an order ID in the search field; the list filters as you type.
Part of the ID is enough. For order #344, searching 344 finds it.
Switch between views
The Monitor opens on All orders. Two quick views narrow it down:
Only successful: everything that went through
Only errors: the orders that need you
Reading the order rows
Every order shows one of three states.
⚫ No document
No document was created for this order yet. Next to it you see why, for example:
Skipped by your exception: order has tag influencer. The order matched one of your Skip these orders exceptions in Settings.
Based on your trigger settings, this order hasn’t triggered any document. None of your triggers has run for it.
Generate document: opens the manual generation window, where you pick the document to create.
🟢 Success
The document was created in inFakt. Open or download it in inFakt.
Under the document you see what happened to its email:
Email sent to …: the customer got it.
Email sending is turned off for this document in Settings. Not an error.
The order has no email address, so there was nobody to send it to.
🟡 The document was created, but inFakt couldn’t send the email. The document is fine and is never created twice. Click Contact us and we'll check it.
A failed email isn't sent again automatically.
inFakt can't email credit notes, so they have no email line.
📷 [IMAGE: inFakt Monitor: a Success row with its email line (canvas board infakt-MonitorOrders, order #23245)]
🔴 Error
The document wasn't created. This is almost never a problem with your data or the app: usually one small setting on your side fixes it, and the row tells you which one. You see the error code, what went wrong and how to fix it, right there.
Try again: opens the manual generation window, where you can pick any document type and create it again
Send to support: opens the chat with the error log attached, so you don't have to explain anything.
🤗 We're on it. Your error log goes straight to our technical team. You always hear back from us, and we stay on it until your document is created.
Email notification, only when it matters
If something failed during the day, we send you a summary email with the affected orders, so you know to open the Monitor. No email means nothing to fix.
Looking up an error code
You don't need this table to fix an error: the Monitor shows the explanation and the fix on the order row. Use it to look up a code you've seen.
Error code | 💬 Explanation | ✅ How to fix |
1-1 | App access denied: subscription not approved or app not in development mode. | Approve the subscription to this Shopify app. |
1-3 | Shopify isn't connected to your invoicing service. | Go to the app settings and set up the connection with your invoicing service credentials. |
2- | Some order data needed for the document is missing. | Try creating the document by hand from the order. If it still fails, contact us: https://makeiteasy.app/contact/ |
3- | Something went wrong on our side while preparing the document. | Please contact us, we'll help as soon as we can: https://makeiteasy.app/contact/ |
4- | The call to the invoicing service failed. We may have sent wrong data, or the problem is on the invoicing service's side. | Please contact us, we'll help as soon as we can: https://makeiteasy.app/contact/ |
4-1 | inFakt already has an invoice with the number this one would get. | In the app's Settings, under Numbering, set a format that gives every invoice its own number, for example one with {{order_number}} in it. Then try again. |
4-2 | inFakt didn't accept the VAT rate of one of the items or the shipping. | Check that the VAT rates on the order are available in your inFakt account (for example, an account that isn't a VAT payer can't issue invoices with 23% VAT). Then try again. If the rates are right, contact us: https://makeiteasy.app/contact/ |
Make sure the trigger isn't 'Never' » If a document type is set to "Never" in the Trigger settings, it isn't created. That's the setting, not a bug.