Notifications: What the Admin Warns You About

A great deal of what your online store does happens without you having to sit there and watch. Orders are transferred to your accounting system, shipping labels are retrieved from the carrier, payments are processed, emails are sent out, and webhooks trigger actions in other systems. When something goes wrong, you’re rarely sitting in front of the screen at that exact moment. That’s why Shoporama collects all notifications in one place, on the Notifications page.

The page explains it itself: “Many of the processes in Shoporama happen in the background, so we aren’t always able to provide feedback immediately.” This is the store’s list of errors and warnings, and it’s worth checking once a week. A single notification can be the difference between an order you get paid for and one where the money was never withdrawn.

How to Find the Notifications

Notifications aren’t listed as a menu item on the left side. You can access them in three ways:

1. The bell icon in the top right corner. The icon changes color when there are notifications in the store. Click on it to expand a small list with the heading “Notifications” and the five most recent messages, including the date and time. At the bottom, there are two options: “Clear All” and “View All.” “View All” takes you to the full overview.
2. Directly via the URL. Type /webshop/notices after your admin URL—that is, right after the shop number in the address bar.
3. On mobile and small screens. Open the menu, scroll down to the “Your Account” heading, and select “Notifications.”

If you use this page often, you can create a shortcut. While on the page, click the star icon "Shortcuts" in the top menu, select "Create Shortcut," give it a name, and tap Save. The shortcut will then appear under the "Shortcuts" heading in the left-hand menu.

How to Read the Overview

The page itself is a table with four columns. “From” shows which system the message comes from, for example, “QuickPay,” “E-conomic,” “PostNord,” “Tema,” or “Webhook.” "Message" is the text itself, often written by the system that encountered an error, so some messages are in English and contain technical details. "Count" indicates exactly how many times that specific message has been received from that exact source. If the number is greater than 1, you can hover your mouse over it to see when the message first appeared. "Latest " is the time of the most recent occurrence. On the far right is a red delete button that removes all instances of that specific message from that specific source.

Because messages from the same source are grouped on a single line, duplicates don’t clutter the list. If you receive the same configuration error from your financial system 40 times in a day, it appears as a single line with the number 40. This makes it easy to see whether something is a one-time glitch or an ongoing problem.

Filter, search, and clean up

There are two filters above the table. In the “From” field, you select one source at a time, and the list shows only the sources that have actually sent something to your store. The “Search in message” field searches for your text within the messages, so you can enter an order number, a product name, or a portion of the error message. If a filter is active, a “Clear” button appears. If you have many notifications, 25 lines are displayed at a time with pagination at the bottom.

The “Remove All” button at the bottom deletes all notifications in the shop, not just the ones you’ve filtered. The same button is available in the bell menu. There is no undo option, so it’s best to clear them line by line using the red delete button. If the list is empty, the page simply displays “No notifications.” If you have a filter enabled, it will instead say “No notifications match the filter.”

What the individual notifications mean

The source in the “From” column tells you where to look. Here are the groups you’ll encounter most often.

Payments and payment gateways

Sources such as QuickPay, Nets Easy, OnPay, Mollie, ePay, PensoPay, Flatpay, Stripe, Payson, and PayPal. This is the most important group, as it involves money.

• "The amount was NOT debited. The payment provider rejected the debit, so the order has not been paid." The order is there, but the money hasn’t come through. The message includes the order number and the gateway’s own explanation, and the order is also marked in the order list. See the article on processing payments.
• "The amount could not be debited because the order total is higher than the amount the customer authorized at the time of payment." You added something to the order after the customer’s authorization. Reset the order to the original amount, or create a new order for the difference and send the customer a payment link.
• "You need to specify an API key to create a payment link" and similar messages regarding a missing private key, checkout key, or Agent ID. The gateway has not been fully configured. Correct this under Store, Integrations, Payment Gateways.
• "Checksum did not match—check merchant secret." Your ePay gateway is missing a valid merchant secret, so Shoporama cannot verify that the response comes from the gateway. Fix this immediately.
• Fraud messages preceded by an order number mean that the gateway has flagged the payment as suspicious. Check the order before packing.

Shipping, labels, and return slips

Sources such as PostNord, GLS, DAO, DHL, DPD, Burd, and “Shipping.” These messages typically appear when a shipping label could not be generated.

• "Production customer number missing," "Shipping method missing," "DPD login failed," and "DHL returns not set up (username, password, or receiverID missing)" all indicate that an agreement has not been fully completed in the shipping setup.
• "You cannot create return labels for orders without tracking numbers" means that a package must have been shipped before the return label can be generated.
• Messages containing an order number and the carrier’s own error message come directly from the carrier. Most often, this is due to an address, a ZIP code, or a weight that they do not accept. Correct the order and resend it.
• The “Shipping” source may warn that a shipping method is still displayed at checkout even though the cart exceeds the method’s maximum weight. The built-in Shoporama themes handle this automatically, but a custom-built theme must mark the method as unavailable itself. The warning is displayed no more than once a week, so it doesn’t clutter the list.

If you’re experiencing many errors with GLS, there’s an article specifically about that: Errors when transferring to GLS.

Accounting Software and Bookkeeping

Sources such as E-conomic, Dinero, and Billy. The messages here are usually very specific:

• “SKU number missing for ...” indicates that a product is missing an item number. The E-conomic integration automatically adds one, but it’s easier to get it right from the start than to correct it later.
• Messages about missing IDs for discount codes and missing IDs for the shipment mean that the discount or shipping costs cannot be posted because a reference is missing from the setup.
• "No API key," "Missing account ID," and "The connection to Dinero has expired. You must reconnect." mean that the integration needs to be set up or renewed under Store, Integrations, Accounting System. Otherwise, the orders will remain pending.
• "We are not transferring the order because it was already transferred" is a warning about double-posting. Transfer it manually if the order actually needs to be included.

The most common errors and their solutions are listed in " Common Errors in the E-conomic Integration."

Theme, Shopping Cart, and Email Templates

This group most often results in lost sales because it concerns what the customer sees.

• "Theme" with the text "Error in your theme at the address ..." means that a page in the store crashed. The address is included in the message, so you can go there directly. "Possible error at the address ... The page was empty" means that the page returned no content at all.
• "Shoporama" with the text "Missing method..." means that your theme is calling something that doesn't exist or isn't allowed in themes. The message specifies which template and which address the issue occurred on. This is a task for your theme developer, or for you to handle yourself in the code editor.
• "Template error" with the text "It is possible to add items to the cart without a variant" is a serious issue for inventory management. Customers can place orders without selecting a size or color, and then you won’t know what to pack. The page’s URL is included in the message.
• "Cancellation" indicates that a customer did not receive a confirmation of their cancellation because the email template mails/withdrawal_received.html is missing from the theme. The confirmation is required by law, so contact the customer manually and make sure the template is in place.
• "Return Center" alerts you if the return label template is missing (return_label.html or mails/return_label.html), and "out_of_stock_mail" indicates that in_stock_mail.html is missing, so customers on the waiting list won’t be notified when the item is back in stock.

Emails, SMS, and Mailing Lists

The “Mail” source displays the mail server’s own error message and the address it applied to—typically an incorrect recipient address or a recipient who rejected the email. You can see what was actually sent in the overview of sent emails. The sources Mailchimp, Klaviyo, Brevo, and Campaign Monitor report when sign-ups cannot be forwarded. “API key missing,” “List ID missing,” and “You must specify a list in the settings” mean that the integration is not complete. You can fix this under Store, Integrations, Mailing List. The source “cpsms” shows the response from the SMS provider when an SMS didn’t go through.

Webhooks, imports, subscriptions, and miscellaneous

• "Webhook" shows the address that was called and the HTTP status it returned. A notification is generated for any status other than a 2xx status, indicating that the recipient system is either down, rejected the call, or responded with a redirect. See the article on webhooks.
• "Import" notifies you if an image or file could not be retrieved, for example, "Incorrect file type. Only jpg and png allowed." or "We could not import ...".
• "Subscription" notifies you when a subscription is missing a customer, or when a subscription order was created with products that were out of stock. The products are listed in the message so you can reorder them.
• "Card Change" notifies you when a customer has changed the payment card on their subscription, but the change could not be saved. Either the store’s payment connection could not be found, or the confirmation from the payment gateway could not be approved. Check that the store has an active payment connection and that the subscription is linked to the correct one, as described in the article on subscriptions. Then ask the customer to change their card again.
• "Split Test" notifies you when a test is complete and which variant won, and warns you if the distribution between the variants appears skewed.
• "Offer Price" alerts you if an end date is in the past or if the start date is after the end date. The date will be ignored, so check the campaign. “Automatic Inventory Status” alerts you if the path to your inventory file is invalid. And “AI” alerts you if your OpenAI key was rejected. Correct it or remove it, and Shoporama will use its own.

What should you address first?

If the list is long, tackle it in this order: first, anything indicating that a payment wasn’t processed, because that costs you revenue right now. Next, the message about a missing cancellation receipt, which is required by law. Then, errors on the store itself—such as “Error in your theme” and “It’s possible to add items to the cart without a variant”—which affect all customers, not just one. Finally, missing keys and configuration issues, which cause the same errors to occur repeatedly until they’re fixed. Accounting and other integrations are important, but can usually be addressed retroactively.

Get theme errors sent directly to your email

Notifications are not automatically sent via email. However, there is one exception that you can enable yourself: errors from your theme. Go to Account, Web Store, General, select the “Theme” tab, and fill in the field “Send error messages from your theme to the addresses below (separated by commas).” That way, those addresses will be notified immediately when a page in the store crashes. This is especially useful if you have an external theme developer who needs to respond quickly.

Notifications clean up after themselves

The list doesn’t grow indefinitely. Notifications older than 14 days are automatically deleted. However, this means the page isn’t an archive. If you need to save a message for documentation, copy the text into the order notes while it’s still there.

For the tech-savvy

• The lines are grouped based on the combination of the source and the exact message text. Two messages that differ by only one character—such as an order number—therefore count as two separate lines.
• The search field looks for your text as a substring within the message itself. It does not search the source name; use the “From” filter for that.
• The "Delete" button on a line removes all instances with the same source and the same message text, not just the most recent one. "Remove All" clears the entire store’s list regardless of the filter. Notifications are specific to a single online store, so if you have multiple stores, you’ll need to switch stores to view their messages.

Frequently Asked Questions

Why can’t I find Notifications in the menu?

Because the page isn’t listed as a menu item. You can access it via the bell icon in the top right corner and the “Show All” option, or by typing /webshop/notices after your admin address. If you want to pin it to the menu, create a shortcut using the star icon “Shortcuts” in the top menu.

Is it dangerous to click “Remove All”?

No, it doesn’t affect orders, products, or customers. But the messages will be gone for good, and there’s no undo option. If there’s a message you haven’t understood yet, leave it alone. If you only want to clear a single type of message, use the red delete button in the row instead.

How do I know if a notification is serious?

Look at the source and the wording of the message. Anything regarding amounts that weren’t charged, receipts that weren’t sent, or errors with the store itself should be addressed immediately. Messages that begin with “You need to specify…” indicate that a setup is incomplete. Messages stating that something “had already been transferred” are typically just informational.

Can I receive notifications via email or in another system?

Only theme errors can be forwarded automatically. You can enable this under Account, Webshop, General, on the “Theme” tab, in the field “Send error messages from your theme to the addresses below.” For the rest, you’ll need to check inside the admin panel, but the bell icon changes color as soon as there’s a new message.

Should I save the notifications for my accountant or bookkeeping?

The notifications are not accounting records, and they are automatically deleted after 14 days. However, messages from your accounting system are a good indication that something has been omitted from the books. Correct the setup and check the affected orders in the financial system while you still remember.

I’ve received the same message 200 times. What does the number in “Count” mean?

The number indicates exactly how many times that specific message has been received from that exact source. Hover your mouse over the number to see when it first appeared. A high number almost always indicates a single recurring configuration issue, not 200 separate incidents. Fix the cause, and the count will stop increasing.

What does “Missing method” from the Shoporama source mean?

It means that your theme is calling a function that doesn’t exist or isn’t available to themes. The message includes which template and which URL the issue occurred on. The customer typically sees a blank field where the value should have appeared. Forward the message to your theme developer, or fix it yourself in the code editor.

I’m getting shipping errors on orders I’ve already shipped. How do I find them?

Select the carrier in the “From” field and enter the order number in “Search in message.” Shipping notifications almost always include the order number, so you can go directly to the correct order. If the error message is from the carrier itself, it’s usually related to the address, ZIP code, or weight.

Why does the bell menu show the same message multiple times?

The bell menu displays the five most recent messages in the order they arrived, without merging duplicate messages. If the same error occurs five times in ten minutes, it will fill the entire menu. Click “Show All” for a grouped overview, where duplicates are consolidated into a single line with a count.

If you’re unsure about a message you can’t resolve, please email support@shoporama.dk with the text from the “Message” column and the source it came from. That way, we can quickly see what went wrong.