Manage Your Store with AI: Get Started with Claude and MCP

Imagine if you could type “show me today’s orders” or “create a 10% discount code called SOMMER26 that expires on June 30,” and your online store would just do it. You can do that in Shoporama. You connect your store to an AI assistant, type commands in plain Danish, and it carries out the actions exactly as if you were sitting in the admin panel and clicking around yourself. It requires no programming and no developer. Shoporama is approved and listed in Claude’s connector library, so if you use Claude, you can connect your shop with just a few clicks.

What is MCP in practice?

MCP stands for Model Context Protocol and is an open standard for how an AI assistant can communicate with another system. Think of it as a universal power outlet: Shoporama provides the outlet, and the AI assistant plugs it in.

Without MCP, an AI chatbot can only talk about your online store based on what you type into the chat yourself. With MCP, Shoporama provides a set of tools—that is, specific actions such as “retrieve an order,” “create a product,” or “find search terms with no results.” When you ask for something, the AI selects the necessary tools on its own. At the time of writing, Shoporama has over 200 of them. Because MCP is an open standard, you’re not locked into a single assistant, but the guide in the admin panel is based on Claude from Anthropic.

How to Get Started

There’s no on/off switch in the admin panel—you’ll need to enable it first. “Enabling” involves connecting an AI client. If you’re using Claude, the easiest way is to connect via Claude’s connector library, where Shoporama is listed. This way, you won’t need to copy any URLs for your first store. You can also find the guide in the admin panel under Integrations, Manage the Store with AI, where you click Get Started. You must have the Full Access role on the store to connect.

Connect from Claude’s connector library (recommended)

1. Open Shoporama in Claude’s connector library and log in to claude.ai if prompted. If you don’t have an account, create a free one. You can also find Shoporama within Claude, including in Claude Desktop and the app: go to Customize → Connectors, click +, search for Shoporama, and click on it
2. Click Connect
3. Claude will open a login window for Shoporama. Log in with your Shoporama account and select the correct store from the list. Read the warning below before clicking next
4. Select the access level. “Read” is selected by default. If you want Claude to be able to make changes in the store, select “Full.” Then click “Authorize Access”
5. Start a new chat and try, for example, “Show me the latest 5 products”

The library works on all Claude plans, including the free one. If you’re using Claude Team or Enterprise, an owner of your Claude organization must first enable connectors. After that, each employee with the Full Access role can connect on their own. If you can’t find Shoporama in the library, make sure you’re logged in to claude.ai. You can also always connect as a custom connector using your MCP URL, as described under “Do you have multiple shops?” further down.

The library is also available in the Claude app for iOS and Android, so you can connect directly from your phone. Anthropic still considers this a beta feature on mobile. Custom connectors, on the other hand, can only be added from claude.ai in a browser or from Claude Desktop, but once the connection is added to your account, it also works on mobile. Then you can ask about today’s sales or place a phone order while you’re in the warehouse.

Your MCP URL: for additional shops, Claude Desktop, and other AI clients

Go to Integrations, Manage the Shop with AI, and click Get Started. At the top, you’ll see Your MCP URL with a Copy button next to it. You don’t need this address when connecting your first shop from the library. You’ll need it when connecting an additional shop as a custom connector, when setting up Claude Desktop manually, and when using an MCP client other than Claude. It looks like this:

https://www.shoporama.dk/mcp?mineksempelshop.dk

The last part—that is, what comes after the question mark—is your own shop’s domain. This makes the address different from shop to shop, which is why you can connect multiple Shoporama shops to the same AI account. More on that below. Always use the URL that appears on your own page, and copy it from the specific shop in question.

Claude Desktop on Mac or Windows

Claude Desktop also has the connector library, so the easiest way is the same as on claude.ai: find Shoporama and click Connect. The configuration file below is only for those who prefer to set up the connection manually.

Claude Desktop uses a small helper process called mcp-remote to communicate with MCP servers on the web. It runs automatically via npx, so you don’t need to install anything yourself.

1. Download Claude Desktop from claude.ai/download
2. Open Settings, Developer, Edit Config
3. Add the block below under `mcpServers`, using your own MCP URL. Remember to end it with your shop’s domain
4. Save the file, and completely close Claude Desktop using Cmd+Q or Alt+F4
5. Restart the program. The first time you send a message, a browser will open where you’ll log in to Shoporama, select your shop, and grant permission

"shoporama": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://www.shoporama.dk/mcp?mineksempelshop.dk"
  ]
}

Do you have multiple shops? Then each shop gets its own connection

Many people have more than one online store. A web agency might manage twenty client stores, and a retailer might have both a live store and a test store. They can all easily be connected to the same AI account at the same time.

From the connector library, you can connect one shop per Claude account. This is because the library uses a single fixed address without a domain, and Claude only allows one connector per address. You must therefore connect each additional store as a custom connector using the store’s own MCP URL. This URL ends with the store’s domain and is therefore different from store to store. At the same time, the domain acts as a label, so you can see in the list of connections which store a given connection belongs to.

On the free Claude plan, you can only have one custom connector. This allows for a maximum of two shops: one from the library and one as a custom connector. If you want to connect more, you’ll need a paid Claude plan. You can also still connect all your shops as custom connectors, including the first one. On the Team and Enterprise plans, an owner adds the custom connector under the organization’s settings.

Connect an additional shop as a custom connector

1. Log in to the admin panel of the shop you want to connect, go to Integrations, Manage the Shop with AI, click Get Started, and click Copy next to Your MCP URL
2. Open claude.ai in a browser on your computer, or open Claude Desktop. Go to Customize → Connectors, click +, and select Add custom connector
3. Enter the store’s name under “Name,” and paste the MCP URL under “MCP server URL”
4. Click Continue. Claude will automatically detect the login settings, so leave them as is and click Add
5. Click Connect. Log in to Shoporama and select the same store as the one associated with the address. If you want Claude to be able to make changes in the store, select Full. Then click Authorize Access
6. Switch to the next store in the admin panel, retrieve its MCP URL, and repeat

If you’re using an AI client other than Claude, establish the connection using the shop’s MCP URL and authorize it with the correct shop in the same way.

The advantage of this model is that each store operates independently. You can set “Read” access for the stores from which you only retrieve data, and “Full” access for the one you’re working in. You can revoke access to one store without affecting the others, and each store has its own audit log. On the other hand, there is no automatic transfer between shops. If you want to move a campaign text from one shop to another, you must ask the AI yourself to retrieve it from one place and create it in another.

If you have both a live shop and a test shop active at the same time, be extra clear in your message about which shop you’re referring to. Changes to the live shop go live immediately. A good tip is to only keep the connections enabled that you’re currently using, and to name your custom connectors after the shop’s name or domain, rather than calling them all “Shoporama.” The connection from the library is named Shoporama, so remember which shop you selected for it.

Which tools does the AI have access to?

The tools are divided into 14 areas, which you can see under “Customize Tools.” Under each area, there’s a link that shows how many tools the area contains. Click on it to see the full list of names. The areas are:

• Catalog: products, variants, categories, brands, suppliers, reviews, product SEO status, and inventory with locations, batches, and cost prices
• Orders: orders, status updates, notes, tracking, shipping labels, order labels, and importing orders from your previous online store
• Customers: customers, customer groups, B2B companies, profile fields, loyalty points, customer statistics
• Marketing: discount codes and campaigns
• Newsletter: Create newsletters, modules, lists, and subscribers. The AI cannot send them
• Page Designer: homepage, modules, and scheduled pages such as a Black Friday homepage
• Theme and CSS: theme files, custom CSS, settings, stylesheet
• Content: blog posts, pages, landing pages, help articles
• Image library: images, folders, and alt text in your image library
• Navigation: menus, URL redirects, 404 errors
• Statistics: sales, profit, products, inventory, marketing, keywords with no results
• Shipping: shipping methods, shipping rates, countries
• Operations: returns, picking lists, inventory entries, messages from the store
• Settings: selected settings for the online store

In addition, there is a small group called Basic Info. It is always active so that the AI knows which store it is communicating with, and it cannot be turned off.

In everyday use, it might sound like this: “Create a phone order for three black wool hats for Bo Jensen, Vestergade 12, 5000 Odense,” “Which 404 errors should I set up redirects for?”, or “Create a Black Friday homepage that automatically goes live on November 28 and takes down on December 1.” A campaign or a scheduled homepage typically takes half an hour to put together. In a nutshell, it takes less than a minute, and you’ll have time to review the result before it goes live.

Statistics and Pre-built Reports

The AI can also answer questions about your numbers: sales and profit margins, bestsellers, slow-moving items, conversion rates, discount codes, and new versus returning customers. It can compare these figures to the previous period or the same period last year. Five pre-built prompts are included: Weekly Report, Purchasing Suggestions, Month-End Closing, Dead Stock, and Searches with No Results. Where you find them depends on your AI client. Read more in Statistics and Reports with Claude.

Inventory, Shipping, Operations, and Settings

The AI can move items between warehouse locations, create batches, set minimum stock levels and cost price, retrieve the pick list, mark orders as picked, and mark returns as received. It can adjust shipping rates, free shipping thresholds, and which shipping methods apply in a country, and it can change selected settings such as store name, search, inventory management, and order emails. Within the theme, it can set multiple settings at once, and it modifies your stylesheet in small increments so that the rest of your CSS isn’t overwritten.

Photos and PDFs from the chat

If you attach photos or a PDF in a chat with Claude—whether in the mobile app, Claude Desktop, or on claude.ai—Claude can send the files directly to your store. It can attach photos to, for example, a product, a category, or a blog post, and it can also save them to the image library. It can attach a PDF to a product as a data sheet. So you can take three photos of a new item and write, “Create the product based on the three images I’ve attached.” This requires one setting in Claude: add www.shoporama.dk under Settings → Capabilities in the “Additional allowed domains” field. You can do this on claude.ai in a browser or in Claude Desktop, and then start a new chat. In Shoporama, the Image Archive section must also be set to “Read and Edit ” under “Customize Tools.” Read more in “Images from Claude.”

What the AI Can’t Do

It’s just as important to know where the limits lie. There are no tools for:

• Sending newsletters. The AI can create a draft and show you a preview, but you’ll need to send it yourself in the admin panel
• Refunding or changing your payment settings. It cannot refund a payment, and it cannot change your payment gateways
• Changing the fundamentals of your store. It doesn’t touch users, roles, domains, currency, whether prices are displayed with or without tax, the mail server, theme selection, or your Shoporama subscription
• Creating or deleting shipping methods. It can edit your existing shipping methods, shipping rates, and countries, but you must create new shipping methods and weight ranges yourself in the admin panel
• Deleting orders. It can update and cancel an order, but not delete it
• Working in a store other than their own. A connection can only view the one online store it was authorized for

Please note that the AI may initiate actions that involve the transfer of funds. If it changes an order’s status to “Shipped” or “Picked Up,” the payment may be charged if your store charges for shipping upon dispatch. If it cancels an order, a card payment will be canceled at the payment gateway, and this cannot be undone. A payment that has already been processed will not be refunded upon cancellation. The AI can also mark an order as paid, for example, after a bank transfer. Before changing the status, it can show you what the change will trigger, and it can change the status of up to 25 orders at a time.

However, the AI can both view and edit customer data if the “Customers” section is set to “View and Edit.” If you don’t want customers to be involved, set the section to “View Only” or “Off” under “Customize Tools.”

And an important caveat: an AI assistant can make mistakes and misunderstand an instruction. Treat it like a skilled but new employee, and ask it to show you what it will do before it does it when making major changes. New products are created as hidden drafts unless you ask the AI to publish them immediately. If it deletes a product by mistake, it’s a soft delete, so you can retrieve it from the Trash in the menu or ask the AI to restore it. Note that a restored product returns as offline, so it must be put back online.

Choose which areas the AI is allowed to work with

On the “Customize Tools” page, you can choose between “Read and Edit,” “Read Only,” and “Off” for each area; at the top, you’ll see “Active Tools ” with two numbers. The number updates immediately when you change the setting, so you can see the effect before clicking “Save.” This setting applies to each individual store; if you have multiple stores connected, you’ll need to set it for each store. Your existing areas retain the access they previously had, while the newest areas—Delivery, Operations, and Settings—start in Read-only mode.

There are two good reasons to restrict access. The first is security: if you want to view information about your orders and customers but don’t want them to be modified, set the sections to Read-Only. If you don’t want the AI anywhere near your theme, for example, select Off. The second is practical: when the AI connects, it retrieves the entire list of tools, and that takes up a significant portion of the conversation. Some users see the error message “This conversation is too long” even before they’ve written anything. If you change a level in the middle of a conversation, the AI may still attempt to process the request until it reconnects, but the attempt will be rejected by Shoporama and logged. More details in “Customize which AI tools are active.”

Security: Access, Logs, and How to Disconnect

Authorization takes place on Shoporama

When you connect an AI client, it redirects you to an authorization page on Shoporama, where you’ll eventually click “Authorize Access.” This applies whether you’re connecting from Claude’s connector library or using an MCP URL. You log in with your regular Shoporama account, and the AI client never sees your password. You’ll choose two things: which online store the access applies to, and what level of access it will have. When connecting an AI assistant like Claude, the levels are “Read” and “Full,” and “Read” is selected by default.

If you want the AI to be able to both view and make changes, select “Full.” If you want to try it out risk-free, stick with “Read.” That way, the AI can still answer questions about sales, bestsellers, and inventory status, but it can’t make any changes. This is a great way to get started.

Only users with the “Full Access” role in the online store can connect the AI. This role applies to your user account in the admin panel and should not be confused with the “Full” access level, which you select for the connection itself. The AI’s tools work across the entire store and cannot adhere to a restricted role. If you have a different role—such as Employee, Marketing, or Developer—or if you’re restricted to specific categories, the authorization page will display the message: “Your role on the selected online store does not grant access to connect the AI. Contact the company administrator.”

It is the role of the user authorizing the connection that matters, not the role of the user typing in the chat. If a colleague uses a Claude account that a user with Full Access has connected, the AI can therefore do the same things as that connection, regardless of the colleague’s own role. If the user behind the connection is later assigned a different role, the AI’s requests will be rejected from that point on. Additionally, only users with Full Access can open Customize Tools, approve changes, and undo actions from the audit log. Read more in Roles and Permissions.

Extra security: Approve changes before they’re made

Under “Customize Tools,” you can enable “Extra Security.” Then, the AI will not make changes that send emails, transfer funds, delete items, or modify multiple items at once. Instead, they’ll wait for your approval, and the AI will provide you with a link to the change, which is valid for 24 hours. When something is pending, it appears at the top of the Manage the Store with AI page, and the menu displays the number of pending items. You’ll see exactly what the AI intends to do and what the consequences might be before you click “Approve and Execute” or “Reject.” Regular changes are still carried out immediately. Read more in “Extra Security: Approve Changes from Claude.”

Everything is logged

Every single time the AI uses a tool, it’s recorded in an audit log, which you’ll find under “View Audit Log” at the bottom of the AI page. It includes the time, which tool was used, the arguments it received, whether it was executed, failed, was rejected, or is awaiting approval, what it may have triggered, and how long it took. The log is maintained per store, so each connection has its own history. Log entries are retained for 90 days. Fields whose names contain words such as “password,” “token,” “secret,” “API key,” or “card number” have their values replaced with [REDACTED] before anything is saved. The actual access key behind the connection is never stored in plain text. Everything about the log is in the AI audit log: see what the AI has done in your store.

Undo a change

If the AI has changed a theme setting, a shipping rate, a web store setting, or your stylesheet, you can click “Undo” next to the entry in the audit log. This only works if no one has changed the value since then. If it has been changed again, nothing will be changed, and you’ll receive a notification so that a more recent change is never overwritten. Emails and other actions that have already been triggered cannot be undone.

Built-in Limits

• Limit on changes. A connection may make a maximum of 120 changes per minute and 3,000 per hour. This stops an AI that has gone into a loop before it reaches the entire catalog
• Text from customers is data. Order comments, reviews, return reasons, search terms, and 404 pages are written by customers and visitors. They are flagged to the AI as data it must never act upon. This protects against so-called prompt injection, where someone hides a message for the AI in, for example, a review
• New products are drafts. A product created by the AI is hidden from customers until you request that it be published online
• Theme settings are verified. The AI can only set options that your theme supports, and invalid values—such as a color in the wrong format—are rejected without anything being saved. Images must come from your image library, and dangerous HTML is removed

How to revoke access

Go to Integrations, API Access. Connections from the AI integration appear on the list with a name starting with OAuth:. Click the trash can icon next to the entry, confirm, and access is revoked immediately. You’d do this, for example, if you’ve authorized the wrong store. Remember that the page always shows the store you’re currently in, so you’ll need to switch to the wrong store in the admin panel to delete its access. On the same page, you can see when each access was last used, what access level it has, and how much of the daily limit it has used. See also Find or Create an API Key.

If an employee leaves, the company administrator simply needs to remove that person as a user from the shop under Company, Users. This will immediately revoke all accesses the employee created via “Sign in with Shoporama” (Claude, the POS app, and the scanner app). The same applies to API keys that the employee created under API Access with a role other than Full Access, such as Developer. Other API keys created manually under API Access are not affected, so you’ll need to delete those yourself.

For those with a technical background

Shoporama’s MCP server communicates via JSON-RPC 2.0 over HTTPS to /mcp. Authentication follows the standard OAuth 2.0 protocol with an authorization code and PKCE, and clients discover all the necessary information themselves via .well-known-metadata. Client registration happens dynamically, so there’s nothing you need to set up in advance. If you want to use an MCP client other than Claude, point it to the MCP URL from the admin panel.

• The query string containing the store’s domain is not read by the server. The endpoint is the same for all stores, and the online store is accessed solely based on the bearer token that the client sends. The domain is a label, not a parameter, so you cannot switch stores by editing the address
• Files that the user attaches in the chat cannot be sent as tool arguments. Instead, Claude retrieves an upload ticket using the ` upload_ticket_create ` tool and sends the files from his development environment as a multipart request to https://www.shoporama.dk/mcp?upload=BILLET. That address does not require a bearer token, as the ticket serves as the access credential. The ticket is valid for 30 minutes for a single store, and the files are not uploaded to the store until Claude uses their `upload_id` through the authorized connection
• The listing in Claude’s connector library uses the endpoint without a query string, i.e., https://www.shoporama.dk/mcp. It’s the same server and the same login flow as with an MCP URL from the admin panel. Because Claude only allows one connector per address, the listing can only connect to one store per Claude account, and additional stores are connected to the address with the domain
• Virtually all MCP tools internally call Shoporama’s existing REST API and thus inherit the same validation, the same access checks, and the same separation between online stores. Only a few lookup tools—including those that search the documentation—bypass this. See the REST API documentation
• Each authorization issues its own token with a limit of 10,000 calls per day. These calls count toward that limit just as they do for other integrations, and usage can be viewed on the API Access page in the Daily Limit column
• Tools are classified as read-only or write-enabled tools, and the list is filtered by both the token’s access level and the scope level under “Customize Tools.” The tools have MCP annotations such as `readOnlyHint` and `destructiveHint`, so clients can ask you before making any changes. If a tool is called anyway, it is rejected with an explanatory error message and logged as “Rejected.”
• The limit of 120 mutating calls per minute and 3,000 per hour applies per token. Rejected calls do not count toward this limit, and a change you have approved under “Extra Security” is not counted again. Some tools also have a limit per call, e.g., 25 orders per status change, 250 customers per import, and 250 orders per import of previous orders
• The server supports MCP prompts with the five predefined reports. They use only the existing tools
• Theme settings are validated against the theme’s `theme_settings.json` file, and themes without that file cannot have settings applied via the AI. The stylesheet is modified using search-and-replace or append operations along with a hash from the read operation, so that a simultaneous change in the admin panel is not overwritten
• Some tools have been removed or replaced; for example, the previous tool for overwriting the entire stylesheet has been replaced by one that modifies sections one at a time. If a client with an outdated tool list calls a removed tool, it receives a message indicating what to use instead
• The tools for theme files require theme file access on the connection. New connections get this automatically, while older ones must be disconnected and reconnected
• Lookups in Shoporama’s support articles, blog, and glossary are located in the Content section. If you disable Content, the AI will also lose the ability to look up information in the documentation

Frequently Asked Questions

Is there an extra cost to use AI in my store?

Shoporama does not charge a separate fee for connecting an AI client. The calls count toward the daily limit on the AI’s access, just like for other integrations, and you can track usage in the “Daily Limit” column under “Integrations,” “API Access.” The AI assistant itself is a product from Anthropic, so they determine what’s included in their subscriptions.

Does it work on the free Claude plan?

Yes. You can connect Shoporama from the connector library on all Claude plans, including the free one. On the free plan, you can only have one custom connector, so you can connect a maximum of two shops: one from the library and one custom connector. If you already have another custom connector, there’s only room for the shop from the library.

Is this the same as the AI button in the text editor?

No. The AI assistant in the text editor writes text for you within the admin panel. This integration is different: you chat in an AI client outside of Shoporama, and it can retrieve data and perform actions across the entire store. The two features do not interfere with each other.

Do the changes made by the AI go live for customers immediately?

Generally, yes—just like when you save changes yourself in the admin panel. This applies, for example, to theme settings, CSS, discount codes, and promotions. A blog post is published immediately, unless you specify a particular date, and discount codes and promotions can also be set with a start date so they take effect only from a specific day. New products are the exception, as they are created as hidden drafts.

Can I send photos from my phone to my products?

Yes. Take the photo, attach it in the chat in the Claude app, and ask Claude to add it to the product. This requires that you add www.shoporama.dk as an allowed domain once under Settings → Capabilities in Claude; you can do this at claude.ai in a browser or in Claude Desktop. If you’re using Claude Team or Enterprise, an owner of your Claude organization manages this setting. Learn more in Images from Claude.

Can the AI write meta titles and meta descriptions for Google?

Yes. The AI can write and edit meta titles and meta descriptions for products, categories, blog posts, pages, and landing pages. For products, categories, and blog posts, it can also set the title and description that appear when the page is shared on social media. If it changes a product’s URL, a redirect is automatically created from the old URL.

Can the AI see the SEO score for my products?

Yes. The AI can read the same SEO status that you see in the SEO card on the product and in the SEO Status column in the product overview: the score from 0 to 100, whether it’s Good, Could Be Improved, or Weak, and what’s missing. It can also sort and filter by status, so you can, for example, type “find the 10 products with the lowest SEO score and suggest what needs to be corrected.”

Products without a primary keyword do not receive a score. The AI can identify them and suggest a keyword, which it can also assign to the product. The status is recalculated shortly after a product is saved. Keep in mind that the score is a checklist for the product page and not a guarantee of ranking on Google. Read more in SEO in Shoporama.

Does the same thing happen as when I place an order myself, for example, with emails and accounting?

Yes. When the AI changes the status of an order, it works the same way as in the admin panel. The customer typically receives a shipping confirmation email, the payment may be processed, and if your accounting software is set to receive orders upon shipment, the order is transferred as usual. If you request it, the AI can skip the shipping email, but “Ready for Pickup” and “Picked Up” always trigger an email. If you ask the AI to send an invoice, it will generally go only to the customer’s email address listed on the order.

Can multiple employees each have their own connection to the same store?

Yes, if they have the “Full Access” role in the shop. Each employee connects using their own Shoporama user account and selects their own access level, so one can have “Read” and another “Full.” “Customize Tools ” and “Extra Security,” however, apply to the entire shop. Each connection appears as its own line under Integrations, API Access. The list does not show which employee is behind each connection, but the User column in the audit log does.

Can an employee with a restricted role, such as Marketing, use the AI?

No, not with their own user account. The AI connection requires the Full Access role, so a role like Marketing does not restrict the AI to the role’s areas but blocks the connection entirely. However, with the Developer role, you can view the “Manage the Store with AI” page and the audit log. If you want to restrict what the AI can do, select “Read” when approving the connection, or set the areas to “Read-only” or “Off” under “Customize Tools.”

Can the AI automatically send me a weekly report?

No, the AI connection does not send reports on its own. The report is generated when you request it, for example, using the pre-built prompt “Weekly Report.” It provides you with revenue, bestsellers, conversion rates, and the items that run out first for the past 7 days compared to the previous week. The pre-written prompts only read and do not make any changes to the store.

We’re an agency with many client stores. What do we do when a client stops working with us?

Remove the connection to the client’s store in your AI client, and delete the access in the client’s store under “Integrations,” “API Access.” If you only delete the access, the connection will stop working immediately, but it will remain as a dead connection in the client. The client’s audit log will not be deleted, so the history of your actions will remain in the store for up to 90 days.

Can the AI see our customers’ personal information?

Yes, if the Customers, Orders, Newsletter, or Operations sections are not set to Off. In Read-Only mode, the AI can view the information, and in Read and Edit mode, it can also modify it. This applies to customers, customer groups, B2B companies, orders with names and addresses, subscribers’ email addresses, and—under Operations—returns and the picking list as well. If you do not want this data to be accessible, set these sections to “Off” under “Customize Tools.” Be sure to take this into account when reviewing your GDPR documentation.

If you’re stuck or unsure whether a change was made by you or by the AI, please email support@shoporama.dk, preferably with a screenshot from the audit log.