Skip to main content

Track and fix document generations on the Dashboard

Everything that happens between Shopify and SuperFaktĂșra, in one place.

The Dashboard is the home screen of the app. Every Shopify order appears here with the status of its documents in SuperFaktĂșra — updated in real time. If a document didn't get generated, this is where you see it, understand why, and fix it without leaving Shopify.

Search by order ID

Type an order ID into the search field and the list filters as you type.

Search works on partial matches, so you don't need the exact format. If your order ID is #344, searching for 344 will find it.

Switch between views

The Dashboard opens on All orders. Two quick views let you narrow it down:

  • Only successful — everything that went through

  • Only errors — the orders that need your attention

Reading the order rows

Every order shows one of three states.

⚫ Not yet

No generation attempt has been made — none of your triggers has run for this order yet.

  • Generate document — opens the manual generation modal, where you pick which document to create.

🟱 Successful

The document was generated in SuperFaktĂșra.

  • Open — opens the document, so you can view or download it.

🔮 Error

The document wasn't generated — but this is almost never a problem with your data or with the app itself. In the vast majority of cases, one small setting on your side is all it takes to fix it, and the row tells you exactly which one: you'll see the error code, a plain-language explanation, and the solution right there. No searching, no guessing.

  • Try again — opens the manual generation modal, where you can select any document type and generate it again

  • Send to support — opens the chat with the error log already attached, so you don't have to describe anything.

đŸ€— We're on it. Your error log goes straight to our technical team and we start working immediately. You'll always hear back from us — we stay on it until your document is created.

Email notification, only when it matters

If there were generation errors during the day, we send you a summary email. It lists the affected orders so you know to open the Dashboard. If everything went through, you don't hear from us. No email means nothing to fix.

Looking up an error code

You don't need this table to fix an error — the Dashboard already shows you the explanation and the solution on the order row. It's here if you want to look up a code you've seen, or understand what's behind it.

Error code

💬 Explanation

✅ How to resolve?

1-1

App access denied: subscription not approved or app not in development mode.

Please, approve subscription to this Shopify App.

1-2

Order total price was 0. We don’t create document in this case.

Create an order with a total greater than 0.

1-3

Shopify is not connected to SuperFaktĂșra using your credentials.

Go to app dashboard and setup your connection using your SuperFaktĂșra credentials.

2-

Some order information is missing for document creation.

Try manual creation directly from the order. If the error persists, contact our support: https://makeiteasy.app/contact/

3-

Something went wrong while preparing the document on our side.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

3-1

Customer is missing from the order. Document creation requires a customer.

Please add a customer to the order, and try again.

3-3

Your Order ID can’t be used as the Variable Symbol because it’s either longer than 10 digits or contains non-numeric characters.

Please update your Order ID prefix/suffix to letters only, or adjust the Variable Symbol settings in the app dashboard.

4-

The API call to SuperFaktĂșra failed. It’s possible we’re sending incorrect data, but the issue might also be on SuperFaktĂșra’s side.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-401

Invalid API credentials

Please, cross-check your connection credentials in SuperFaktĂșra and the app dashboard.

4-402

You don't have an active SuperFaktĂșra premium plan.

This integration is available only with a premium SuperFaktĂșra plan. Please upgrade your account to proceed.

4-403-1

SuperFaktĂșra API limit reached.

Please try again tomorrow using the manual creation option under Shopify → Orders, or upgrade your plan to increase your daily limit.
​

4-1

Failed to retrieve bank accounts from SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-2

Failed to connect to SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-3

Failed to send document email via SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-4

This is a dashboard action. Failed to fetch sequences from SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-5

Failed to delete document on SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-6

Failed to mark document as paid on SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-7

Failed to create document on SuperFaktĂșra.

Please contact support for assistance, we help you as soon as possible: https://makeiteasy.app/contact/

4-7-1

The document wasn’t created because a document with the same numbering already exists.

Try using a unique numbering sequence, or reach out to SuperFaktĂșra for help: https://www.superfaktura.sk/en/

4-7-2

Incomplete profile in SuperFaktĂșra

Please complete your SuperFaktĂșra profile to resolve this issue and create documents. Go to: SuperFaktĂșra » Log in » Profile » Fill in all required data

Ensure Trigger is not set to 'Never' » Maybe, under Trigger settings you have set "Never" option to the document you want to create, you it is blocking the creation. Soo, it is not a bug, but a feature.

Did this answer your question?