Infigo’s Storefront Configuration Problem Solvers (Q&A) hub. This space brings together a growing collection of concise, targeted articles designed to help you fine-tune your storefront setup. Whether you’re exploring a specific feature, solving a niche configuration challenge, or looking for practical guidance within the Infigo admin area, you’ll find clear, focused support right here.

How Do I Enable Approval Navigation in the My Account Area?

When the Approval Workflow is active, customers expect to see an easy-to-use navigation option in the My Account section to review pending order approvals. In some cases, the expected dropdown may not appear even though the approval process is functioning.

This article provides guidance on verifying and enabling the necessary setting to ensure that the Approval navigation populates correctly for users. It also explains alternative ways to access the approval page if the dropdown is missing.

Use cases

Customers trying to review pending approval requests from the My Account section.
Administrators needing to ensure that the storefront navigation for approvals is correctly displayed.

Key settings in the Platform

Show Approval Links: Located in the Editable Content > Header section within the platform administration panel. This setting must be enabled to display the approval dropdown in the My Account area.

Step-by-step guide

Log into the platform's administration panel.
Navigate to the Editable Content section and open the Header settings.
Locate the Show Approval Links option and set it to Yes.
Save the changes and refresh the storefront. The approval dropdown should now appear under the My Account section.
If the dropdown still does not appear, try clearing your browser cache or reviewing the configuration to ensure the setting was saved correctly.

How Do I Fix Incorrect Approval Email Links?

This article explains why your order approval emails may contain an incorrect store URL and how to resolve the issue. The problem typically occurs when the store URL in the Workflow Settings is misconfigured.

If the Workflow Settings contain an outdated or incorrect URL, automated emails will include non-functional links. In addition, if the default placeholder (such as 'teststore') appears in the URL, it indicates that the specific storefront name was not correctly updated in the configuration.

By following the steps outlined below, you can update your Workflow Settings to ensure that approval emails direct you to the correct page. This guide is designed to prevent future occurrences of this issue.

Use cases

An order approval email directs you to a URL that results in an error.
The URL displays a default or placeholder storefront name instead of the actual store name.

Key settings in Infigo

Store URL: Located in the Workflow Settings under the admin panel.
Custom Binding: Ensure your storefront custom binding is correctly set if you are using a non-standard URL.

Step-by-step guide

Log in to your Infigo admin panel and navigate to the Workflow Settings section.
Locate the field for the Store URL and check its current value.
Update the Store URL to the correct value, for example:
- https://yourstore.example.com
- or your custom binding (e.g., yourstore.example)
Save your changes in the Workflow Settings.
Generate a new order approval email to ensure the updated URL is used; note that previously sent emails will still contain the old link.
Test the approval link to confirm it directs to the correct page.

How Do I Fix Incorrect Out-of-Stock Messages?

Sometimes product pages display an out-of-stock error for certain sizes even when inventory is available. This issue may occur when the system still holds inventory amounts as on hold, causing a mismatch between actual stock and what the customer sees.

In some cases, the inventory for product variations is not properly updated when orders are placed. This can result in product variants showing available stock in the backend, yet the storefront displays an out-of-stock message.

A common resolution is to clear the on-hold inventory amounts via the admin interface. Once cleared, the product page should accurately reflect available stock and allow orders to reduce inventory as expected.

Use cases

Product pages showing an out-of-stock message despite available stock.
Inventory counts not reducing after customer orders are placed.
Discrepancies between stock information in the admin panel and the storefront display.
On-hold inventory amounts affecting attribute combination stock settings.

Key settings in Infigo

Product Variant Inventory: Accessible via Admin > Product Variant Edit to review stock levels and attribute combinations.
On-Hold Inventory: Located within the inventory management section where on-hold amounts are recorded for products that have shipped.
Order Management: Check if orders are correctly decrementing the inventory and managing on-hold stock.

Step-by-step guide

Log in to the admin panel and navigate to the Product Variant Edit page for the affected product.
Review the stock levels for each product size, paying close attention to the on-hold inventory amounts.
If the on-hold value is causing the error, use the delete button to clear the on-hold amount for the specific variants (e.g. XS and 2XL).
Save your changes and refresh the product page to verify that the out-of-stock message is no longer displayed.
If the issue persists, confirm whether your inventory is managed manually or via an external MIS system to further troubleshoot the discrepancy.
Contact Customer Support for additional guidance if necessary.

How Do I Import Products with Images?

This article explains how to import a large number of products along with associated images using the Upload Folders feature. It covers the requirements in your CSV file and the necessary steps to ensure that product images are correctly mapped and removed from the upload area once imported.

When importing products to your storefront, you need to have your images stored in the Upload Folders area. The CSV file that you import must include a column named ProductImage that references the exact file name of each product image.

This guide outlines the process, common use cases, the key settings inside the system, and step-by-step instructions to help you successfully manage your product imports without having to repeatedly ask the same questions.

Use cases

Importing a large catalog of products for a new storefront.
Adding product images efficiently as part of a bulk upload process.
Managing and updating product image assets via a centralized upload area.

Key settings in the system

UploadFolders access: Ensure that the user role has permission to access the UploadFolders area.
ProductImage column: In your CSV import file, include a column named ProductImage with the exact file names of your images.
Upload Location: During the import process, select the correct upload location where the images are stored.

Step-by-step guide

Upload all your product images to the UploadFolders area.
Prepare your CSV file ensuring it includes a ProductImage column with the file names corresponding to the uploaded images.
Start the import process by selecting the appropriate upload location that matches where your images are stored.
Once the CSV is imported, the system will map the images to the respective products and remove successfully mapped images from the UploadFolders area.
If issues arise during the import, verify that the file names in your CSV are accurate and that you have the correct access permissions.

How Do I Resolve Sitemap URL and Namespace Errors?

This article explains how to address common sitemap issues such as invalid relative URLs and missing XML namespaces. These issues typically occur when sitemap entries are not fully qualified and proper namespace definitions are missing.

When a sitemap contains relative URLs (for example, a URL like /FAQs) or an incorrectly declared XML namespace, search engines like Google may reject the sitemap submission. It is important to ensure that all URLs are fully qualified with the complete domain and that the XML is correctly structured.

The primary cause of these issues can be linked to the handling of canonical URLs and language culture settings in the system. In particular, blog posts or FAQ pages may show unqualified URLs if a canonical URL is specified incorrectly. Updating or removing the canonical URL can allow the system to automatically generate a fully qualified URL.

Use cases

Submitting a sitemap to Google Search Console and encountering URL errors
Blog posts or FAQ pages showing relative URLs in the sitemap
Errors related to missing or incorrect XML namespace declarations

Key settings in Infigo

Canonical URL: Located in the blog post or page editor under the SEO settings
Sitemap Generation: Verify settings in the Sitemap plugin to ensure correct URL formatting
Language Culture: Check the settings that affect how URLs are rendered based on language or location

Step-by-step guide

Log in to your admin panel and navigate to the affected blog post or FAQ page.
Locate the SEO section where the canonical URL is set.
Ensure the canonical URL is a fully qualified URL (e.g. https://www.example.com/FAQs) rather than a relative URL.
If you choose to remove the canonical URL, the system will automatically generate a full URL for you.
Save your changes and regenerate your sitemap.
Resubmit the updated sitemap to Google Search Console.
Monitor the Search Console for any further errors.

How Do I Resolve the Invalid Platform URL Error?

When creating a new storefront, you might encounter an error stating that the Platform URL is not correctly configured. This error usually occurs because the URL is missing the required protocol (https://) at the beginning of the address.

This guide explains why the error occurs and provides step-by-step instructions to update your Platform URL setting so that it includes the necessary https:// prefix.

Following these instructions will resolve the error and prevent it from reoccurring, ensuring that storefront creation works seamlessly for all platform administrators.

Use cases

Error encountered during storefront replication when logged in as platform admin.
Instances where the Platform URL was entered without the https:// prefix.

Key settings in Infigo

Platform URL: Located in the Administration > Settings > Platform Configuration section.

Step-by-step guide

Log in to your platform as an administrator.
Navigate to the Administration section and select Settings.
Go to the Platform Configuration settings where the current URL is displayed.
Ensure that the URL begins with the protocol https:// (for example, https://yourdomain.infigosoftware.com/).
Update the URL if necessary and save the changes.
Test the storefront creation process to confirm that the error is resolved.

How Do I Restrict Checkout to a Single Item?

This article explains how to restrict customers to only one line item per order using the Maximum basket items setting available in the Cart Settings. This configuration is ideal for scenarios where you want to limit purchases and simplify the checkout process.

When this setting is enabled, customers can only add one distinct product to their basket. Although the system may still display a success notification when an additional item is attempted, only one item will appear in the cart.

Recent updates have addressed some messaging concerns by displaying a brief notification on the cart page if the maximum item limit is reached. This guide details how to configure these settings and offers additional tips to ensure a smooth customer journey.

Use cases

Enforcing single-item purchases during limited-time offers or promotions.
Restricting purchases of high-value or sensitive products to avoid bulk orders.
Simplifying the checkout process by limiting shopping cart complexity.

Key settings in Infigo

Maximum basket items: Located in the Cart Settings, this option allows you to define the maximum number of distinct items a customer can add to their cart.
Checkout Requirements: Found under Checkout Settings, this area lets you add custom rules to the checkout process to reinforce purchase limitations.

Step-by-step guide

Log in to your Infigo administration interface.
Navigate to the Cart Settings section.
Locate the Maximum basket items setting.
Set the value to 1 to restrict the cart to a single line item.
Save your changes and test the storefront to ensure the setting behaves as expected.
If additional restrictions are required, visit the Checkout Requirements under Checkout Settings to configure custom checkout rules.

How Do I Preselect a Specific Shipping Address at Checkout?

This article explains the behavior of the address selection during checkout. The system is designed to automatically use a saved default billing or shipping address if available, even if the option to preselect the first address is turned off.

When a customer has no default address set, the system can preselect the first available address from either the user record or the address book if the setting is enabled. However, if a default address (typically a billing address) already exists, the system will continue to display that address.

This design aims to reduce user errors and streamline the checkout process. Nevertheless, it might lead to unintentional selections when an address is not actually the customer’s intended choice.

Use cases

A customer without a default billing or shipping address, where preselecting the first saved address can guide the checkout process.
A customer with an existing default address, leading the system to automatically display that address during checkout.

Key settings in Infigo

Preselect first address: Located in Configuration > Settings > Customer Settings. This setting is intended for accounts without a default address.

Step-by-step guide

Verify whether the customer record contains a default billing address. If one exists, the system will continue to display that address.
If no default address is set, ensure that the Preselect first address option is enabled so the system automatically selects the first available address.
To test changes, clear browser and system caches, then navigate back to the checkout process.
If the behavior is not as expected, consider removing or updating the default address in the customer record to see the effect.
If a placeholder such as 'Please choose a shipping address' is desired instead of a preselected option, note that this is not currently supported when a default exists. You may consider submitting a feature request.

How Do I Fix Order Quantity Limit Errors?

This article explains why you might receive a warning message when trying to add a specific quantity of a product to your cart. The error may occur even if your requested total is below the maximum allowable quantity.

The system enforces a set maximum order quantity for each product. If you already have some units in your cart, the remaining amount you can add is reduced to ensure that the total does not exceed the limit.

In some cases, a different limit may appear if you are logged in as another user who already has additional units in their cart. Clearing previous selections can help resolve the issue.

Use cases

A customer adds units to their cart and receives a warning when trying to exceed the maximum order limit.
A customer trying to add a new quantity finds that the allowed amount is lower due to existing units in the cart.
An instance where impersonation or multiple sessions lead to higher than expected values already in the cart.

Key settings in Infigo

Maximum Order Quantity: Found in the product configuration under Order Settings.
Cart Contents: Displayed on the shopping cart page to show current units in the order.

Step-by-step guide

Review the product details to identify the maximum order quantity set for that item.
Check your cart to see how many units are already added for that product.
Calculate the remaining number of units you can add by subtracting the current cart total from the maximum allowed.
If the allowed addition seems lower than expected, confirm that you are not logged in as another user with additional units in the cart.
If needed, clear the cart and start a new order to avoid any conflicts.

How Can I Force Confirm Deletion in Shopping Basket?

When a customer decides to remove their job(s) from the shopping basket, you can now display a confirmation dialog to the end user in order to prevent accidental job deletion.

To enable this feature, login with your Administration account

Then navigate to Configuration -> Settings -> Basket setting -> Locate " Confirmation prompt before removing from basket" and check the tick box

Click Save, and now the deletion functionality in the basket will force a confirmation prompt.

How Do I Configure a Discount Requirement on Basket Total?

This is a completely new discount type. It is one that allows you to apply a discount to a basket total when the user has over a specified amount.

For example,
If shopping basket total is over £200 apply discount 1
This only works on the subtotal (not including delivery or tax)

Setup

Contact us about installing the plugin on your platform. Once installed you are free to setup the discount. Navigate to Promotions > Discounts and create a new discount. Give it a relevant name, set the type to ‘Assigned to order subtotal’, configure the discount amount, start end date etc. as you wish then click ‘Save and Continue Edit’.

Setting up the discount

In the admin page, navigate to Promotions > Discounts.

Click 'Add new' (top right)

Give the Discount a name that is relevant (maybe include the product you are applying it to for your own reference)

From the drop down choose your discount type.

Choose whether you want to discount a static cost or a percentage of the price.

Click 'Save and Continue Edit', then navigate to the Requirements tab and set the requirement type to ‘Customer’s basket value is x.xx’ and then lastly set the basket total threshold (this is the amount that will trigger the discount should their basket total go over that figure)

Save the requirements

How Do I Configure Storage Control Settings for Baskets / Carts and Saved Projects?

We have clean-up functionality to various job elements aimed at keeping surplus job information to a minimum whilst saving space on your system.

These updates primarily control the expiration of baskets, saved baskets and saved projects, and have been placed in a new Storage Control section of your Order Settings along with some existing related settings.

To support these warning settings above, there are email templates:

These settings ensure you do not get a backlog of defunct data on your Storefront, by ensuring a timely clean-up.

How Do I Configure MiniBasket for Accurate Line Item Count?

When multiple quantities of a single product are added, the default display reflects the cumulative quantity. Enabling the proper setting ensures that the mini-basket counts each product line item once regardless of its quantity.

Follow this guide to configure your basket settings easily so that customers see a clear and accurate count of items in their basket.

Use cases

One product with a high quantity displays as a single line item instead of the total quantity.
Multiple products with varying quantities reflect the accurate number of line items.

Key settings in Infigo

Total Product Count Ignores Quantity: Located within the Basket Settings under the Product Count Options. Hover over the setting for an explanatory tooltip to confirm its purpose.

Step-by-step guide

Log in to the Infigo admin interface.
Navigate to the Basket Settings section.
Locate the Total Product Count Ignores Quantity option.

Hover over the tooltip to read a detailed explanation of the setting.

Enable the setting to have the mini-basket display the number of unique line items instead of the cumulative quantity.
Save your changes and test the mini-basket display on your storefront.

How Do I Add a Custom Binding to My Storefront?

This article will help explain the process of how to add a new URL to your storefront. If you also plan on obtaining an SSL to secure your site, we have to complete the binding first. You can read this article on the steps for implementing an SSL if you would like to obtain a certificate for your new domain.

Please note, that implementing a new binding will accrue the following charge:

UK: £15 + VAT / USD $18 / €18 / AUD $30 / CAD $26

Pre-Requisites

Prior to raising a ticket for us to configure a domain binding for you, you will need to have purchased your domain so that you can configure your DNS.

A majority of our customers purchase their domains through GoDaddy or 123Reg, but please use whichever service you prefer.

What We Need

When raising a ticket for configuring a new domain, please be sure to provide the following:

Current Storefront URL (e.g. yourCompany.infigosoftware.com/storefrontName)
New domain URL.

The Process

After raising a support ticket with the above information, a support team member will raise a formal task to our development team to implement this new domain against the storefront requiring this binding.
When the binding has been applied to your site, it will be part of the the next release. We deploy every 2 weeks and the agent will inform you of when you can expect your binding to be live on your storefront. Note: This task will need to be raised to the development team a few days prior to one of our releases otherwise it will have to be included in the next release.
Once released, the support team will provide you a CNAME record to point this new domain towards. Note: This must be configured in your DNS. This is not a task Infigo can carry out as it is something you need to do with your hosting provider.

Please Note:

This process can take up to 2 weeks to complete.

Once everything is done and the new binding has taken effect you will need to manaully update you header and footer links. Please see Changing Header/Footer Links After Adding a New Binding for how to do this.

How Do I Set Up and Use Reward Points on My Storefront?

Infigo allows your customers to earn reward points and use them to get money off of their future orders. You can control when they earn these points, how many points they earn, and set the exchange rate between points and the store currency.

Configuration

Enabling the feature

To enable the reward points feature on your storefront, go to Configuration > Settings > Reward Points > tick the enabled box > click save.

Configuration

The reward points feature offers the following settings that allow you to configure the feature to behave how you want it to:

Enabled:

This determines whether or not the feature is active.

Exchange rate:

This setting allows you to set the monetary value of reward points

Points for registration:

This sets how many points will be awarded to the user when they register.

Points for purchases:

This sets how many points the user will be awarded for making a purchase.

Awarded order status:

This allows you to control the status which the order must reach before the user is awarded their points. For example, if you set the order to "Complete" then they will be awarded the points when you mark the job as complete. Alternatively, if you set it to "Processing" then they will be awarded the points as soon as payment has been confirmed.

Cancelled order status:

This allows you to set the status used to determine if the points should be removed. By default this is set to "Cancelled" so that if a user cancels their order, they lose the reward points granted by that.

How they work

End users will find Reward Points in their My Account. They'll see how many points they've earned, the monetary value of their points, and the history of orders placed toward those points:

During checkout, the customer will be able to check "Use my reward points" and the monetary value of the reward points will be removed from the order subtotal. If their points cover the entire cost of the order, then payment will not be requested from the user. Otherwise, the user will pay for the rest of the order as normal.

Infigo Admin Users can manage a users' reward points in Customers > Customer Management > Edit the user and to go the Rewards Points tab

How Do I Edit and Manage Customer Reward Points Adjustments on My Storefront?

This guide explains how to effectively manage, edit, and delete reward points adjustments in your storefront using Infigo’s web-to-print platform. Whether you need to correct a mistake, audit changes, or manage permissions, this article provides step-by-step instructions. It also highlights critical scenarios where recalculations are required and points out restrictions that ensure system integrity.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content.

2. Contents

Overview
Contents
Key Points and Takeaways
Key Settings
Scenario-Based Guide
- Scenario 1: How to Edit Reward Points
- Scenario 2: How to Delete Reward Points
- Scenario 3: Auditing Reward Points Changes
FAQs
Alternate Search Terms

3. Key Points and Takeaways

Editing Reward Points: Adjusting points or messages automatically recalculates subsequent balances. Adjustments related to placed orders are locked.
Deleting Reward Points: Soft-deleting entries recalculates balances, keeps historical data for deleted entries.
Auditing: Every action (add, edit, delete) is logged, with timestamps and user details for transparency.
Permissions Management: A new Admin ACL protects reward points access and ensures that only authorized users can manage them.
Negative Balances: Balances can go negative, but reward points cannot be used for payment until a positive balance is restored.
Insights Integration: All adjustments and audit data sync with Insights for reporting.

4. Key Settings

1. Enable Reward Points Management

Path: Admin Area → Configuration → Settings → Reward Points
Explanation: Ensure these settings are configured to allow editing and deleting of reward points.

3. Editing Reward Points Per Customer

Path: Admin Area → Customers > Customer Management > Edit [Any customer] > Reward Points tab
Explanation: This area is where reward points are applied and tracked within Infigo on a customer level.

5. Scenario-Based Guide

Scenario 1: How to Edit Reward Points

Problem: An incorrect message or points value was added to a customer’s reward points history.
Solution:

Navigate to the Customer's Edit page and select the Reward Points tab. (Admin Area → Customers > Customer Management > Edit [Any customer] > Reward Points tab)
Click the Edit button next to the reward points entry.
Adjust the message or points value:
- Message Edit: Directly update the text.
- Points Edit: Changing points recalculates subsequent balances automatically.
Save the changes.
- Note: Edits to points associated with orders are restricted.
Verify the updated balances in the reward points history.

Scenario 2: How to Delete Reward Points

Problem: A reward points entry was added incorrectly and needs removal without deleting it from the database.
Solution:

Navigate to the Customer's Edit page and select the Reward Points tab. (Admin Area → Customers > Customer Management > Edit [Any customer] > Reward Points tab)
Click the Delete button next to the entry.
Confirm the deletion. The entry will now appear grayed out.
Use the “Show Deleted” checkbox to toggle visibility of deleted entries.
Verify subsequent balances have been recalculated.

Note: Reward points adjustments tied to placed orders cannot be deleted.

Scenario 3: Auditing Reward Points Changes

Problem: A store admin needs to track who made changes to reward points and when.
Solution:

Open the Reward Points tab in the Customer Edit page.
Look for the following audit columns:
- Created On: Date of the original entry.
- Updated On: Last modification date.
- Customer/Creator: Name or API token of the user who made the change.
Navigate to the Activity Log to view detailed entries, including the old and new values and recalculation details.

6. FAQs

Q1: Can reward points have a negative balance?
Yes, balances can go negative, but reward points cannot be used for payment until the balance becomes positive again.

Q2: Can reward points for placed orders be edited or deleted?
No, reward points adjustments linked to orders are locked to maintain transactional integrity.

Q3: How do I check recalculated balances after editing?
Recalculations are visible immediately in the Reward Points tab. Ensure all updates reflect correctly after editing or deleting an entry.

Q4: What does soft-deleting a reward points entry mean?
Soft-deleting retains the record in the database by graying it out, with visibility controlled based on the “Show Deleted” filter.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content.

How do I Enable a Shipping-Specific Email Address for Storefront Orders Using the New “Contact Details for Order Notifications” Setting?

This article addresses the scenario where a user on the public storefront wants to define an email address specifically for the shipping address during checkout. While this functionality can be configured from the Infigo Admin backend, allowing customers to enter a shipping-specific email directly on the storefront ensures smoother operations and improved reporting and notification capabilities.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content.

2. Contents

Overview
Contents
Key Points and Takeaways
Key Settings
Scenario-Based Guide
- Scenario 1: How to enable email address entry for shipping when placing an order
FAQs
Additional Resources

3. Key Points and Takeaways

To ensure the shipping address email is used for notifications instead of the customer’s main profile email, you should:

Set “Contact details for order notifications” to Billing or Shipping address details.
Enable “Address email address required.”

These adjustments ensure the email field appears and is required when adding a new shipping address. This setup also ensures that the email specified in the shipping address is used for notification and reporting, rather than defaulting to the customer’s main email.

4. Key Settings

Setting 1: Contact Details for Order Notifications

Path: Infigo Admin > Customer Settings > Contact details for order notifications
Explanation:
This dropdown replaces the old boolean setting customersettings.usecustomeremailforcorrespondence.
- Customer details: Uses the customer’s main profile email for notifications.
- Billing or Shipping address details: Uses the email defined in the billing/shipping address during checkout.

To ensure that the shipping email is actually used, select Billing or Shipping address details.

Setting 2: Address Email Address Required

Path: Infigo Admin > Customer Settings > Address Email Address Required
Explanation:
Enabling this setting makes the email field mandatory when a user adds or edits an address. By requiring an email for each shipping address, notifications can be sent specifically to that address.

5. Scenario-Based Guide

Scenario 1: How to enable email address entry for shipping when placing an order

Problem:
Customers want to provide a shipping-specific email address during checkout, but the storefront currently does not show or require an email field for shipping addresses.

Solution:
Follow these steps:

Log in to the Infigo Admin panel.
Navigate to Customer Settings to locate the relevant configurations.
Set “Contact details for order notifications” to Billing or Shipping address details.
- This ensures that notifications draw the email from the shipping (or billing) address instead of the customer’s main profile.
Enable “Address email address required.”
- This setting makes the shipping address email field mandatory whenever a customer adds or edits a shipping address.
Save your changes.
Test the storefront:
- Go to the public storefront as a customer.
- Add a new shipping address during checkout.
- Verify that the email field is now visible and mandatory.
- Complete the order and confirm that notifications use the shipping email address.

6. FAQs

Q1: What happens if “Contact details for order notifications” is set to “Customer details”?
If you set this dropdown to Customer details, the notifications will use the customer’s main contact email, and any shipping-specific email address will not be used for order emails.

Q2: Why is it important to enable “Address email address required”?
Enabling this setting ensures every shipping address includes an email, allowing for accurate communication and reporting. Without this requirement, users may skip the email field, resulting in missing or incomplete notification information.

Q3: Can this be configured on a per-storefront basis?
Yes. These settings are configurable per storefront in the Infigo Admin panel, which means you can have different behavior across multiple storefronts if needed.

Q4: Is this change retroactive for existing addresses?
No. Existing addresses will not be updated automatically. If you need an email for an older address, you or your customers may need to edit it manually.

How do I Implement Accessibility Features on My Storefront?

This guide explains how to use Accessibe, a third-party accessibility tool, to enhance your storefront's accessibility features. Accessibe provides automated solutions such as screen reader compatibility, keyboard navigation enhancements, and user-adjustable accessibility profiles.

Please note that Accessibe is not a supported feature within Infigo, and this article is intended to provide general information on integrating third-party accessibility solutions. If you choose to implement Accessibe, you are responsible for testing and maintaining the script on your storefront.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content: Infigo Academy.

2. Contents

Overview
Contents
Key Points and Takeaways
Key Settings
Step-by-Step Guide
FAQs
Alternate Search Terms

3. Key Points and Takeaways

Accessibe Overview: Accessibe provides automated tools for improving website accessibility, such as screen reader optimization and keyboard navigation adjustments.
Infigo Support: Accessibe is a third-party tool and not a supported feature within Infigo.
Script Placement: Add the Accessibe script to the Page Footer Container in Infigo settings for application across storefront pages.
MegaEdit Compatibility: Applying the script to MegaEdit pages may cause issues. It is advised to avoid this unless absolutely necessary, in which case the script can be placed into an Editable Content block for testing purposes.
User Responsibility: Users are responsible for testing and maintaining the Accessibe script on their storefront.

4. Key Settings

Page Footer Container:
- Path: Infigo Settings > PageFooterContainer
- Explanation: Place custom scripts like Accessibe here to apply them to all storefront pages.
MegaEdit Content End (Optional, highly recommended to implement on a test storefront first):
- Path: Content Management > Editable Content > MegaEdit Custom Content
- Explanation: If you need to test Accessibe on MegaEdit pages, you can input the script here. Be aware that this may cause the editor to malfunction, and its use is not recommended for production environments.

5. Step-by-Step Guide

Step 1: Obtain the Accessibe Script
Log in to your Accessibe account and retrieve the script provided for your website.

Step 2: Access Infigo Admin Settings

Log in to your Infigo Admin Dashboard.
Navigate to Infigo Settings > Page Footer Container.

Step 3: Add the Accessibe Script

Paste the Accessibe script into the Page Footer Container field.
Save your changes.

Step 4: Test Accessibe on Your Storefront

Open your storefront in a browser and verify that the Accessibe interface appears and functions as expected.
Test its features, such as screen reader compatibility and keyboard navigation, to ensure proper implementation.

Step 5: MegaEdit Compatibility Considerations

Avoid applying the Accessibe script to MegaEdit pages, as this may cause the editor to lock up or malfunction.
If you must test Accessibe with MegaEdit, input the script in the MegaEdit Custom Content field within Editable Content settings.
Test thoroughly in a non-production environment to assess the impact on functionality.

6. FAQs

Q: What is Accessibe, and how does it help?
A: Accessibe is a third-party tool that enhances website accessibility with features like screen reader compatibility and keyboard navigation adjustments.

Q: Is Accessibe supported by Infigo?
A: No, Accessibe is not a supported feature within Infigo. This article provides guidance for integrating third-party tools, but implementation and maintenance are the user’s responsibility.

Q: Can Accessibe be used with MegaEdit pages?
A: It is recommended to avoid applying the Accessibe script to MegaEdit pages, as it may cause functionality issues. If absolutely necessary, you can test it by inputting the script in the MegaEdit Custom Content field in the Editable Content page.

Q: How do I maintain Accessibe on my storefront?
A: As Accessibe is a third-party tool, you are responsible for maintaining the script, testing its functionality, and ensuring compatibility with updates.

How do I Install a New Language to your Storefront?

You need your Infigo storefront to display in a language that is not currently installed or active. You go to Admin > Configuration > Languages (sometimes referred to simply as the “Languages” list) and see the language listed as inactive or with an “Install Language” button—but you’re unsure how to enable it so it appears live on your storefront.

2. Installing and Activating a New Language

Log in to your Infigo Admin Area.
- Make sure you have the correct admin permissions to modify language settings.
Access the “Languages” List.
- Navigate to Admin > Configuration > Languages (naming may vary slightly depending on your Infigo version).
Check if the Language Is Already Installed.
- If the language is not installed, you should see a button labeled “Install Language” next to it.
Install the Desired Language.
- Click “Install Language” for your desired language. This queues the language pack for installation.
Wait for an Infigo Deployment.
- After clicking “Install Language,” the platform typically requires a scheduled deployment to finalize the language installation.
- Tip: You’ll usually see a note at the top of the Languages page informing you that the new language will be available after the next deployment.
Verify Installation & Publish/Enable.
- After the deployment, check back in Admin > Configuration > Languages. Your new language should show as installed.
- Click "Edit" next to your desired languge and set the "Published" option on the subsequent screen.

3. Troubleshooting & Common Questions

“Install” Button is Not Clickable or Language Shows as Not Installed
- Ensure you have admin permissions to modify languages.
- Try logging in as a platform administrator.
- Verify that a deployment hasn’t already been queued. Sometimes the button remains inactive while the process is pending.
Language Still Not Available After ‘Install’
- Wait for the next scheduled deployment or overnight sync.
- If it still doesn’t appear a few days later, contact Support or verify the deployment schedule.
Language Resources Are Missing or Partially Translated
- Some languages might have partial translations depending on the completeness of the language pack.
- You can manually adjust resource strings via Admin > Configuration > Languages > Edit Resources to fill in missing phrases.

4. Further Learning & Support

Infigo Academy
Access step-by-step tutorials, video walkthroughs, and more advanced topics on language configuration at:
https://academy.infigo.net/academy/c/51/browse-all
Need More Help?
If you still encounter issues, reach out to Infigo Support with screenshots or a detailed description of the error.

Summary

Changing or adding a new language in your Infigo storefront is a straightforward process:

Go to Admin > Configuration > Languages.
Click “Install Language” next to the desired language.
Wait for the system deployment or overnight sync to complete.

Following these steps ensures your store is accessible to customers in their preferred language.

How Do I Resolve an Invalid platform URL Error When Creating a Storefront?

If you encounter the error message 'Invalid platform URL. The platform URL is not correctly configured.' while creating a new storefront in Infigo, it is likely due to an incorrectly formatted URL within General Settings. This article explains how to resolve the issue by ensuring the correct format is used.

The Platform URL must include the full protocol prefix (i.e. https://) to be accepted by the system. This requirement was introduced following a platform update to improve URL validation and security.

Once the correct format is applied, the error will no longer appear and you will be able to create new storefronts successfully.

Key settings in Infigo

Platform URL: Navigate to Configuration > Settings > General Settings > Storefront URL

Step-by-step guide

Log in to your Infigo Admin account with Platform Admin privileges.
Switch storefront and choose the Platform level
Go to Configuration > Settings > General Settings > Storefront URL.
Ensure the URL includes the full protocol prefix. For example, instead of yourstore.infigosoftware.com/, it should be https://yourstore.infigosoftware.com/.
Click Save to apply the changes.
Retry creating the new storefront. The error should no longer appear.

How Do I Restrict Storefront visibility through Departments and Access Control?

Access control has been added to Infigo to allow Categories and Products to be restricted from view for specific Customers.

The Access Control system checks these against a Customer's Role or Department.

Generally Customers viewing the site will have the same Role (Registered) and therefore it makes more sense to base this visibility on Department.

Creating a Department

Go to Configuration > Departments

Click "Add new record" to add a new Department

Give the department a Name, Description, Cost Code, PL Code. The most important thing here is Department Name.

Save your Department.

Assign Users to Departments

Expand the Department using the + on the left of the Department name.

From the list, tick each user you wish to assign to this Department, then click "Save Changes".

Access Permissions

As default, a Storefront has Access Permissions switched off.

Go to Configuration > Settings > Access Permission Settings

Switch on Access Permission Enabled

The Default Is Allowed switch determines whether the site shows All Categories when you are not in a Department or none.

Default Is Allowed = True means that all Categories show up if users are not in a Department

Default Is Allowed = False means that all Categories are hidden until a user is assigned to a Department that can use them.

Include Children in Category Access = When enabled we will check the subcategories and the products inside a category to determine the access to a specific category.

It is best practise to make sure that Default Is Allowed is set to false and that you specifically allow departments access to what you would like them to be allowed access to as this will prevent further access.

For example, if you have a department "Department A," you have the categories "Category A" and "Category B," and you only want customers in Department A to see products in Category A, you would take the following actions:

Set Default Is Allowed to False

Create a rule allowing Department A to access Category A (this will include the products within the category).

Since Default Is Allowed is set to False, the customers in Department A will only be able to see Category A and its products, so they will not have access to Category B.

Deny Guest Accounts should always be ticked as true.

Setting Department Permissions

From the Admin menu, go to Catalogue > Access Permission > Setup Access Permissions

The top of the page confirms your Storefronts Access Permission settings (detailed above)

Below this you can select the Role or Department you wish to assign a restriction/access to.

Once you select a department, a secondary menu appears asking you what area of the site you wish to target. General site use would be covered from either Products or Categories.

Select a target, and click Load.

This loads all possible options for the site. Each option has a tick box to 'apply' access to, and once ticked, you can the grant access to it or leave unticked to restrict access.

Save the mappings when complete.

Impersonate the user or use the Access Permissions test in the same Infigo menu.

How Do I Switch between B2B and B2C storefronts?

Infigo allows the administrator to specify whether a storefront is protected by login (B2B) or open to the public to view all the full catalogue (B2C)

The change is a simple adjustment to each storefront.

Admin > Configuration > Settings > Customer Settings

Locate the setting Closed Store: Login Required. Tick this box if you wish to enforce B2B functionality. Leave it unticked if you wish to allow users to browse the store without login.

You may also wish to change the registration method. B2B sites generally do not allow registration. From the drop down list Registration Method select Disabled and the registration form will be removed.

Save all changes

What you need to know about the Storefront Status: Test Mode

When creating a new storefront it will be launched in "Test Mode". You will see a reference to this in Storefront Management and when logged in with your Platform Account, you'll see it alongside the storefront name on "Current Storefront".

Here is an example from one of our Infigo Training platforms:

Test Mode:

allows you to build your storefront in a "testing" environment before going to live
means you can easily remove test data (orders, users, etc) before moving to live
gives you and your colleagues a clear indication as to which storefronts are live, and which need more work before they're ready for external use.

Clearing Test Data

When updating a storefront status to Live, you will be given the option to "Clear Test Data":

You will be advised on the impact of doing this - "Are you sure you want to clear test data for your account? This will remove all test customers and orders from this storefront, the action cannot be undone.".

If you want to review users before clearing test data... here's how:

go to Customer Management and click Edit on the customer you wish to keep after clearing test data. If the user does not have an admin role then you will have the option to Convert to Live (admin users will be 'live' by default).
if you don't want to keep the user when you change storefront status, then don't convert them to live and they will be removed when you clear test data.

When you're ready to clear test data (in Storefront Management), you simply click the button on the right hand side. Please make sure you're on the correct storefront before confirming - this change cannot be undone.

The process will begin after you confirm you are sure you want to clear test data for your account. The process will show in the bottom right corner and once complete you'll get downloads of test orders (for your records).

Switching Storefront Status to Live

So, you've cleared your test data and now you're ready go change the storefront status to Live.

Once again, you need to go to Storefront Management and find the storefront you want to update.
Click on Edit on the right hand side
Choose Live from the Status dropdown and click Live

Then click on Update

How Do I Configure an "All Products" header menu item which works with Access Permissions?

We have some great help content (articles and videos) which will run through how to build category and subcategory menus using content templates.

1. Create an "All Products" Parent Category (this would essentially just be a name for a regular category).

2. Go to the Display Settings tab and tick "show category navigation" in this and all child categories you create under this parent. (The hint explains: enabled this to show the category navigation side menu for this category. Please switch the page to a 1 column layout if you're using 2 column layout).

When this is enabled, the user will see all categories they have access to on the left hand side of the page.

3. If you wanted to fill the empty space on the right hand side of the page (the all products category with with categories based on their access permissions, then you can link the categories to the "all products" category using the Parent Category option within the category like so:

How Do I Add Addresses to Departments?

This article will explain how to add addresses within departments, so that the addresses are available for all users under that department.

***

Department addresses can be added by creating the department, expanding it by clicking on the + sign, and then scrolling down to the 'Addresses' section:

Click on 'Add Address' and enter the information > click Save.

Once you've added all of your addresses go to Configuration > Settings > Customer Settings, scroll to 'Billing and Delivery Address Configuration' and enable 'Include department addresses on billing and delivery selections:'

This will allow users to see the department addresses, and they will be able to add and access their own addresses.

How Do I Add Meta Title, Keywords and Description?

Metadata is data (information) that provides information about other data.

Metadata will not be displayed on the page but is machine parsable so can be used by browsers, search engines or other web services to understand more about the page they are displaying.

The common meta tags use on web pages and those supported in Catfish are Description and Keywords.

Description:

Sometimes used by search engines as the descriptive black text in the search result listing, meta descriptions can help increase the customer click through in search results but will not necessarily impact rankings directly.

Keywords:

Although Meta keywords ceased to impact rankings in 2009, people still use them, albeit with caution.

Title Tags:

Title tags are still the single most important piece of metadata on the page.

The best title tags begin with the most relevant keywords, product name, or article name and end with the name of the site

To set these up on your Catfish storefront you have a number of options.

Storefront wide:

Under Configuration > Settings > General and Miscellaneous Settings : SEO settings tab, you have a number of options to configure.

Page title separator is as the name suggests the the character (or series of characters) that you wish to use to separate your page titles.

Default title will appear as the page title on ALL your website pages, so think carefully before adding text here.

Default meta keywords will get appended as the keyword meta data your ALL your website pages.

Default meta description will get appended as the meta description on ALL your website pages.

Home Page Meta Title allows you to set the page title for just your websites home page. A new setting we added recently in order to provide you with more flexibility.

Home Page Keywords are keywords, again that you can setup just for your website homepage

Home Page Description is the description that you can write that will only populate the home page meta description

As well as these default SEO settings, you will also find a SEO tab on your category pages, product pages and topic pages that give you complete control over the meta data that gets used on each of your pages.

To note: If you do not want the same meta data to be used on all your pages then leave the Default entries blank. Enter in the text for your homepage and then ensure that each of your product, category and topic pages have custom entries for Title, Keyword (if you wish to use it) and Description.

How Do I Configure Department Address Exclusivity Mode?

These two enhancements extend how departments manage addresses in Infigo storefronts.
They introduce options that let you:

Automatically use a department’s billing address for all its members, and
Restrict customers so that only department-level addresses can be used for orders.

This ensures consistent billing data, reduces manual entry, and is especially useful for corporate or franchise storefronts where multiple users share the same financial details.

What’s included

Use Department Address as Billing Address
- Automatically applies the department’s billing address during checkout.
- Skips the manual billing-address step entirely.
- Makes billing fields read-only in My Account and Admin.
Use Department Address Exclusively
- Hides individual customer addresses and replaces them with department-level ones.
- Applies to checkout, My Account, and split-shipping logic.
- Supports VAT and multi-shipping workflows.

Key settings

Use Department Address as Billing Address
Found under Admin → Departments → Edit Department.
When enabled, the billing address step is bypassed, and the department’s billing address is applied automatically.
Use Department Address Exclusively
Also in Admin → Departments → Edit Department.
When enabled, only department-level addresses are available for checkout and account management.
Read-only fields
Billing fields in My Account and Admin become non-editable when these settings are active, preventing inconsistent data.

Use cases

Corporate storefronts: Departments share one billing address for all team members.
Franchise networks: Centralise all orders to a main billing office while maintaining department-level shipping.
Simplified checkout: Reduce steps for repeat B2B buyers by skipping billing entry entirely.
Data integrity: Prevent discrepancies between customer-entered addresses and accounting records.

Step-by-step implementation

Step 1 – Enable billing address automation

Go to Admin → Departments.
Click Edit next to the department you want to configure.
Select the Set as default Department Billing Address

Save changes.

💡 When this setting is active, customers linked to this department will automatically use its billing address during checkout.

Step 2 – Enable address exclusivity (optional)

In the same department settings page, enable Use Department Address Exclusively.

Save your changes.
- Customer address lists will now only display department-level addresses.
- Customers can add or edit department addresses in checkout or My Account, but they won’t appear in their personal address book.

Step 3 – Test checkout behaviour

Log in as a customer belonging to the department.
Add products to your basket and proceed to checkout.
Confirm that:
- The billing step is skipped (if automation is enabled).
- Only department-level addresses appear.
- Read-only fields prevent manual entry.

Step 4 – Validate admin behaviour

Check the Admin → Customers → Addresses section.
Confirm that no duplicate addresses are stored against the customer account.
Ensure the department address appears in the order summary and invoices.

Tips & best practice

Use billing automation for B2B accounts where finance details rarely change.
Combine both settings for full department-level control.
Test with split shipping to confirm correct handling of multi-address orders.
Communicate with users that addresses are managed centrally to avoid confusion.

How Do I Configure Department-Level Billing Address Automation?

These two enhancements extend how departments manage addresses in Infigo storefronts.
They introduce options that let you:

Automatically use a department’s billing address for all its members, and
Restrict customers so that only department-level addresses can be used for orders.

This ensures consistent billing data, reduces manual entry, and is especially useful for corporate or franchise storefronts where multiple users share the same financial details.

What’s included

Use Department Address as Billing Address
- Automatically applies the department’s billing address during checkout.
- Skips the manual billing-address step entirely.
- Makes billing fields read-only in My Account and Admin.
Use Department Address Exclusively
- Hides individual customer addresses and replaces them with department-level ones.
- Applies to checkout, My Account, and split-shipping logic.
- Supports VAT and multi-shipping workflows.

Key settings

Use Department Address as Billing Address
Found under Admin → Departments → Edit Department.
When enabled, the billing address step is bypassed, and the department’s billing address is applied automatically.
Use Department Address Exclusively
Also in Admin → Departments → Edit Department.
When enabled, only department-level addresses are available for checkout and account management.
Read-only fields
Billing fields in My Account and Admin become non-editable when these settings are active, preventing inconsistent data.

Use cases

Corporate storefronts: Departments share one billing address for all team members.
Franchise networks: Centralise all orders to a main billing office while maintaining department-level shipping.
Simplified checkout: Reduce steps for repeat B2B buyers by skipping billing entry entirely.
Data integrity: Prevent discrepancies between customer-entered addresses and accounting records.

Step-by-step implementation

Step 1 – Enable billing address automation

Go to Admin → Departments.
Click Edit next to the department you want to configure.
Select the Set as default Department Billing Address

Save changes.

💡 When this setting is active, customers linked to this department will automatically use its billing address during checkout.

Step 2 – Enable address exclusivity (optional)

In the same department settings page, enable Use Department Address Exclusively.

Save your changes.
- Customer address lists will now only display department-level addresses.
- Customers can add or edit department addresses in checkout or My Account, but they won’t appear in their personal address book.

Step 3 – Test checkout behaviour

Log in as a customer belonging to the department.
Add products to your basket and proceed to checkout.
Confirm that:
- The billing step is skipped (if automation is enabled).
- Only department-level addresses appear.
- Read-only fields prevent manual entry.

Step 4 – Validate admin behaviour

Check the Admin → Customers → Addresses section.
Confirm that no duplicate addresses are stored against the customer account.
Ensure the department address appears in the order summary and invoices.

Tips & best practice

Use billing automation for B2B accounts where finance details rarely change.
Combine both settings for full department-level control.
Test with split shipping to confirm correct handling of multi-address orders.
Communicate with users that addresses are managed centrally to avoid confusion.

How Do I Configure OAuth Authentication for SMTP Email?

Email accounts can now use OAuth 2.0 for secure, token-based authentication instead of traditional username/password logins.
This modernises email security and improves compatibility with providers like Microsoft 365 and Google Workspace.

Highlights

Added OAuth 2.0 authentication support for SMTP
New configurable fields: Tenant ID, Client ID, Client Secret, Token Endpoint, Scope
Backward-compatible with Basic Auth
Enhances email-sending security

How to implement

Go to Admin > Configuration > Email Accounts.
Edit an existing email account or create a new one.
Select OAuth 2.0 Authentication and enter the required credentials.
Send a test email to confirm token-based authentication works.

How Can I Change Date-Picker Localization?

The datepicker component is now fully localisable, allowing translated day and month names and flexible date formats.
This ensures a consistent, region-specific experience for international storefronts.

Highlights

Localized day and month names
Customizable date formats per language
Applies across checkout and My Account forms

How to implement

Go to Admin > Languages.
Edit the desired language and search for keys vue.datepicker.days and vue.datepicker.months.
Update the comma-separated values for days (7) and months (12).
Save and verify translations appear in the storefront datepicker.

Can I use multiple login methods on one storefront?

Yes. Infigo supports multiple login methods within a single storefront, allowing different users to access the same storefront using different authentication mechanisms. These login methods can coexist without conflict and are selected based on the customer’s technical setup and business requirements.

This flexibility makes it possible to support a mix of internal users, external users, and procurement-based access within the same storefront.

Supported login methods

A single Infigo storefront can support combinations of the following login methods:

Standard username and password
Users can log in directly via the Infigo login page using a traditional username and password. This is commonly used for day-to-day access and administrative users.

Single Sign-On (SSO)
Infigo supports Single Sign-On integrations, allowing users to authenticate through an external identity provider. This is often used by organisations that require centralised user management or already have an existing authentication system in place.

Punchout login
Punchout login allows users to access the storefront by initiating a session from an external procurement or ERP system. In this case, users do not log in through the Infigo login page but are instead passed into the storefront as part of the Punchout flow.

Social login

Infigo can support social login methods (for example, Facebook login), allowing users to register or log in using an existing social media account. This option is generally used for consumer-facing storefronts where simplified registration is preferred.

Custom API-driven authentication

For customers with specific or non-standard requirements, Infigo can support custom authentication flows using API-driven methods. This allows integration with bespoke identity management systems where standard SSO approaches are not suitable.

Using multiple login methods together

These login methods can be enabled at the same time within the same storefront. For example, a storefront may allow:

Internal users to log in using SSO
External users to log in with a standard username and password
Procurement users to access the storefront via Punchout

Each user will follow the login flow appropriate to how they access the storefront.

Important limitations to be aware of

While multiple login methods can coexist, the login method itself cannot be used to control storefront behaviour such as:

Product availability
Pricing rules
Payment methods
Checkout logic

Any differences in storefront behaviour must be configured using roles, departments, permissions, or other access control mechanisms within Infigo, rather than relying on how a user logged in.

When should I use multiple login methods?

Using multiple login methods is particularly useful when:

Different user groups require different access paths
Punchout access is needed alongside direct storefront access
A customer is migrating to SSO but still needs to support existing users

USEFUL LINKS:

Why is my site loading slowly and external stock levels not displaying via an integrated system?

This article explains how to diagnose and resolve issues where product pages load slowly and external stock levels are not displayed in the storefront.

It is based on a resolved case where the integration failed to retrieve an authentication token from the external stock system after a network change. The guidance below walks through structured checks to quickly isolate whether the issue lies with configuration, connectivity, or endpoint changes.

Before escalating, complete the checks outlined below and collect supporting evidence (HAR files, screenshots, connector settings) to assist investigation.

Use Cases

Product pages take significantly longer than normal to load.
External stock levels do not display on product pages.
The Add to Basket button is disabled or unavailable.
The issue began after a broadband, firewall, or network infrastructure change.
One storefront works correctly while another does not.

Key Settings to Review

Connect Plugin – API URL
Confirm the endpoint used to contact the external stock service.
Connect Plugin – Credentials
Verify the application ID/email/password used to request an authentication token.
Handle Stock Setting
Ensure the product or connector setting instructs the system to use the external connector for stock handling.
Storefront Connector Mapping
Confirm the connector is enabled for the affected storefront.
Connection Test / Integration Logs
Use the built-in test function to attempt token retrieval and review any error responses.

Step-by-Step Troubleshooting Guide

1. Confirm the Symptom

Open an affected product page and observe:

Page load time
Whether stock appears
Whether Add to Basket is enabled

Document the behaviour.

2. Capture Browser Evidence

Generate a HAR file from the browser Network tab.
Check the Console tab for JavaScript errors.
Capture screenshots showing missing stock or disabled purchase controls.

3. Compare Working vs Non-Working Storefronts

If another storefront is functioning correctly:

Compare connector assignment
Compare API URL configuration
Compare stock handling flags

Differences here often identify misconfiguration.

4. Test the Connector

Use the Connect plugin’s Test Connection feature.

Expected outcome:

A successful authentication token is returned.

If the response is null, empty, or errors:

The integration cannot reach the external service
The endpoint may be incorrect
Credentials may be invalid

5. Verify the API Endpoint

If token retrieval fails, confirm:

The external stock system’s public address has not changed.
The connector is not pointing to an outdated IP address.
The correct hostname or current public IP is configured.

In the referenced case, the external system’s public IP changed following a network migration, and the connector continued referencing the previous address. Updating the API URL resolved the issue.

6. Confirm Network and Firewall Rules

If the endpoint is correct but connection still fails:

Confirm outbound traffic from the integration environment is not blocked.
Confirm inbound firewall rules on the external system allow requests from the integration server.
Verify no recent security rule changes were introduced.

Firewall allowlisting may be required depending on hosting setup.

7. Prefer DNS Over Raw IP (Best Practice)

If the external stock system is hosted on a connection where public IPs may change:

Use a stable DNS hostname rather than a fixed IP address.
This reduces risk of future outages following ISP or infrastructure changes.

8. Re-Test End-to-End

After configuration changes:

Re-run the connector test.
Reload a product page.
Confirm:
- Stock loads promptly
- Add to Basket is enabled
- No console/network errors appear

9. When Escalating to Support

Provide:

Product URLs
HAR files
Console logs
Screenshots
Connector configuration (obscure passwords)
Details of any recent network or ISP changes

Including this information significantly reduces investigation time.

Summary of Confirmed Root Cause (From Resolved Case)

In the validated incident:

The external stock system’s public IP changed following a network migration.
The Connect plugin API URL still referenced the previous IP.
The system could not retrieve an authentication token.
Updating the endpoint resolved both slow loading and missing stock display.

Additional Resources

For further guidance, consult your internal integration documentation or contact your Support team for assistance.

Image Upload and Processing

Max Image Upload Megapixels

Defines the maximum resolution allowed for uploaded images, measured in megapixels.

If an uploaded image exceeds this limit, the system may reject the upload or resize the image depending on other configuration settings.

This helps prevent extremely large images from consuming excessive memory or processing resources.

Scale Down Image if Too Large

If enabled, images that exceed the maximum megapixel limit will be automatically resized instead of rejected.

This allows large images to still be uploaded while ensuring they remain within acceptable system limits.

Collect Image Metadata – Reverse Geocoding

When enabled, the system reads GPS metadata embedded in uploaded images and converts the coordinates into a readable location using reverse geocoding.

This only applies if the uploaded image contains location metadata.

Collect Image Metadata – Facial Data

Allows the system to extract facial detection metadata from uploaded images where available.

This may be useful in advanced indexing or image analysis scenarios.

Collect Image Metadata – Colour Information

Extracts colour profile information from uploaded images.

This data can be used for image processing, classification, or advanced search functionality.

Image Preview and Thumbnail Settings

Thumbnail Size

Defines the size of thumbnails generated for media uploaded by users.

Thumbnails are displayed in album grids and media lists when browsing images.

Preview Size

Defines the size of preview images used when viewing media inside an editor interface.

These settings only affect generated previews.

The original uploaded image file is not modified.

PDF Processing Settings

Convert PDF Files to PNG Image

This is a legacy setting used for the Infigo Editor.

Because the Infigo Editor does not support PDF files directly, this option converts uploaded PDFs into PNG images so they can be used inside that editor.

If Infigo Editor is not used, this setting should normally remain disabled.

PDF Conversion Width

Defines the width of generated preview images when a PDF is converted into a raster image.

This is mainly used when creating previews or thumbnails.

PDF Conversion Resolution

Controls the DPI (dots per inch) used when rasterizing a PDF during internal processing.

Rasterization may occur when:

generating previews or thumbnails
converting PDFs into images
performing image processing on PDF content

Higher DPI values increase image clarity but also increase memory usage.

If this value is set too high, it can cause out-of-memory exceptions during processing.

In most cases, 72 DPI or 96 DPI is sufficient.

MegaEdit typically works with the original PDF file directly, so this setting mainly affects preview generation.

Media Support Multiple Pages

Allows the system to process multi-page PDF documents.

When enabled, individual pages can be processed or previewed separately.

Max Page Counts for PDFs

Defines the maximum number of pages allowed in an uploaded PDF file.

If a PDF exceeds this limit:

The entire file upload will be rejected

This prevents extremely large PDF documents from affecting system performance.

Album Limits and Management

Default Album Item Limit

Defines the maximum number of items allowed in the default album.

The default album is the initial album automatically created for users.

Custom Album Item Limit

Defines the maximum number of items allowed in all additional albums created after the default album.

Can Add Multiple Albums

This is the main switch that determines whether the system supports multiple albums.

If disabled:

only a single album will be available.

By default, only album administrators can create additional albums.

User Can Add Multiple Albums

If multiple albums are enabled, this setting allows regular users to create additional albums themselves.

If disabled:

only administrators can create new albums.

Album Sharing Settings

Can Explicitly Share

Allows users to manually share albums with specific users or groups.

Album Admins See Shared Albums

Allows album administrators to see all shared albums, even if the albums were not directly shared with them.

Share Album Within Department

If enabled, albums are automatically shared with all users in the same department.

This allows department members to access each other's albums without manually sharing them.

Restrict Albums in “Me” to Own and Category Shared

When enabled, the “Me” section only displays:

albums owned by the current user
albums shared via category sharing

This setting was originally introduced for a specific use case and may not be required in most environments.

Show Different User

Displays the user associated with uploaded media items.

This helps identify who uploaded or owns a particular media asset.

Image Conversion Settings

Convert to Grayscale

This feature was originally developed for a specific customer use case and is not commonly required.

If enabled, all uploaded images will be automatically converted to grayscale.

Grayscale Delta Transparency

Defines the threshold used to determine whether a pixel should become fully transparent during grayscale conversion.

The system calculates the sum of the pixel’s RGB values and compares it to the configured delta value.

Grayscale Transparency Factor

Controls how transparency is applied to pixels that are not fully transparent.

The transparency level is calculated using the red colour channel multiplied by the configured transparency factor.

MegaEdit Asset Settings

MegaEdit Small Thumbnail Width

Defines the thumbnail size used for MegaEdit assets, such as:

clipart
masks
other design elements

These thumbnails are displayed within MegaEdit asset libraries.

MegaEdit Layout Thumbnail Size

Defines thumbnail sizes used within MegaEdit layout previews.

Media Usage Tracking

Track Media Item Usage

This option is only required when using certain image plugins that charge per image usage.

Some stock photo integrations (such as Depositphotos) require tracking when images are used within designs.

When enabled, the system records how media items are used so licensing or billing rules can be applied correctly.

Image Processing Limits

Max Transparency Conversion Megapixels

When scaling images that contain transparency, the system uses a specific image processing library that preserves transparency.

However, this library may fail with very large images.

If an image exceeds the configured megapixel threshold:

the system switches to a fallback Adobe-based processing library
transparency will be removed during processing

This setting defines the megapixel threshold where that fallback occurs.

PDF Conversion Resolution Interaction

This setting also works together with the PDF Conversion Resolution setting.

If the rasterized PDF image would exceed the configured megapixel threshold:

the system automatically reduces the conversion resolution to 72 DPI

This prevents excessive memory usage during processing.

Platform-Level Limits

Max Image Preview Width

Max Image Thumbnail Width

These settings define the maximum allowed values for preview and thumbnail sizes within the system.

They are typically restricted to super administrators and used by Infigo administrators to control system limits.

Adobe Engine Compatibility

Check Compatibility with Adobe Engine

Verifies whether uploaded images can be processed correctly by the Adobe rendering engine used in certain workflows.

Fix Adobe Engine Incompatible Images

If an image cannot be processed by the Adobe engine, the system can automatically re-encode the image to ensure compatibility.

These settings are primarily used for support or troubleshooting scenarios.

Advanced Features

Preview PDF Profile Options

This setting allows configuration of custom PDF preview rendering profiles.

It is an advanced feature and generally does not require modification for standard storefront configurations.

How do I Customise my Infigo Job Ticket?

Job tickets display important order information used by production teams. In Infigo, job tickets can be customised to include company branding, layout adjustments, and additional production details.

Customisation is typically handled by the Infigo Professional Services team based on the branding assets and requirements provided by the customer.

What a Job Ticket Displays

A job ticket is generated for each order and may include information such as:

Order details
Product information
Product attributes selected by the user
Uploaded artwork or files
Production notes or instructions

Production teams use this document to review the order and complete fulfilment.

Requesting a Branded Job Ticket

To create a customised job ticket template, the following information should be provided:

Company logo
Brand colours
Any required fonts or styling preferences
A layout example or mock-up (if available)
Details of any additional information that should appear on the job ticket

This information allows the Infigo Professional Services team to create or modify the job ticket template so it aligns with the company’s branding and workflow requirements.

Including Product Attributes on Job Tickets

Additional order information can be displayed on job tickets using product attributes. These may include details entered by the user when ordering a product.

Examples include:

installation location
selected product options
uploaded images
special instructions

Attributes must be configured correctly in the product settings to appear on the job ticket.

Configuring Attributes for Job Tickets

Product attributes are managed in the product configuration.

Location:

Product → Product Attributes

When configuring attributes for job tickets:

The attribute must not be hidden
The attribute should be configured under Attributes (Job Attributes) rather than Admin Attributes

Attributes marked as hidden may display differently or not appear as expected in the job ticket output.

Testing the Job Ticket

After a customised template has been implemented, it is recommended to place a test order to confirm that:

attributes display correctly
entered values appear as expected
the job ticket layout renders properly

Testing ensures the job ticket functions correctly before being used in production.

How to Separate Infigo Job Tickets into a Separate Hotfolder?

In Infigo, job-related documents such as Job Tickets, Packing Slips, and Invoices can be automatically copied to specific hotfolders for use by production or customer service teams.

This allows you to separate job tickets from other production files and send them to a dedicated folder.

Why Use Separate Hotfolders?

Separating job tickets into their own hotfolder can help teams:

organise production workflows
give customer service teams access to job documentation
separate job tickets from artwork or production PDF files
automate document delivery to external systems

For example, production PDFs may flow into one hotfolder while job tickets are copied into another folder used by customer service or administration teams.

Configure Job Ticket Hotfolder Routing

To configure where job tickets are copied, you must update the Hotfolder settings within the admin area.

Step 1

Open the Admin area.

Step 2

Search for:

Hotfolders and Print Locations

Step 3

Open the Hotfolder Settings tab.

Step 4

Locate the section that allows you to copy additional items to hotfolders.

The settings highlighted below allow you to send documents such as:

Job Tickets
Packing Slips
Invoices

to a specific hotfolder location. You can also choose a custom name for packaging slips, invoice filenames and job ticket filenames.

Step 5

Select the hotfolder where you want the Job Tickets to be copied.

Step 6

Save your changes.

How It Works

Once configured, Infigo will automatically copy the selected documents to the configured hotfolder whenever an order is processed.

This allows different files generated during the order workflow to be routed to separate folders.

For example:

File Type	Destination
Production PDF	Production hotfolder
Job Ticket	Customer service hotfolder
Packing Slip	Packing or dispatch folder

Testing the Configuration

After configuring the hotfolder mapping, it is recommended to place a test order.

Confirm that:

the production files appear in the correct production hotfolder
the job ticket is copied to the configured job ticket hotfolder

Testing ensures the routing works correctly before using it in a live workflow.

How do I Renew my SSL Certificate?

Important Please note:

You can purchase SSL certificates for more than one year, but you must renew your certificate every year and raise a support ticket with the renewed certificate. This is an industry standard rule changed on 1st September 2020.

The below CSR information are the required fields needed on the SSL renewal ticket form:

Country Name (full name)

State or Province Name (full name)

Locality Name (e.g. city)

Organization Name (e.g. company)

Organizational Unit Name (e.g. section / department)

Common Name (e.g. your name or your server's hostname, should be exact to the website name)

Email Address

***

We ask that you send us the renewed certificate 2-4 weeks before it is due to expire (This allows for plenty of time for the SSL to be renewed before it expires). SSL renewals without a rush fee* are charged at £75 + VAT / USD $100 / €90 / AUD $145 / CAD $129. If you forget to renew your certificate then we may be able to rush* through the renewal, however the costs for this vary.

Please log into your providers site (for example, 123 Reg, Go Daddy, DigiCert, etc). If you're unsure of how to do this with your given provider, then please go to their help pages for instructions.
Go to your account
Find the SSL in question and there should be a renewal option.
Renew the certificate & download a copy
Please submit a SSL Renewal Ticket,attach the certificate / zip file and confirm the storefront URL. If you have a wildcard SSL, please please also give us the primary domain.
SSL Certificate Renewals are applied to your site and the Support Team will let you know when these are done.

If your certificate is close to expiry or has expired and you would like us to rush* it through then we may be able to do so. To renew an SSL certificate in less than:

5 working days we charge £150 + VAT / USD $200 / €180 / AUD $290 / CAD $258
2 working days we charge £375+VAT/ USD $500 / €450 / AUD $730 / CAD $644

*Rush fees explained: If you need us to apply the renewed certificate on your storefront(s) after the SSL has expored then there will be a rush fee. This is because this task will be put in front of all other tasks to get your renwel completed sooner. We cannot guarantee a rush fee, but we will do our best to accommodate you.

Why Do Multiple Tag Filters on a Storefront Not Narrow Results Together?

When using Tag Filters on an Infigo storefront, you may notice that selecting multiple filters does not always narrow the product results as expected.

This occurs because the storefront filtering logic currently uses an OR condition when multiple Tag Filters are selected. This means the system will return products that match any of the selected tags, rather than only products that match all selected tags together.

As a result, selecting additional filters may broaden or maintain the result set rather than progressively narrowing it.

Example

Imagine a storefront with the following Tag Filters:

Colour = Blue
Size = Large

If a customer selects Colour = Blue, the storefront will show all products tagged with Blue.

If the customer then also selects Size = Large, the results may include:

products tagged Blue
products tagged Large
products tagged Blue and Large

Because the filtering logic matches products that satisfy any selected filter, the results are not restricted to only items that match both filters simultaneously.

How Tag Filtering Works

When multiple Tag Filters are selected:

The storefront evaluates all selected tags.
Products matching any of those tags are included in the results.
Products do not need to match every selected filter to appear.

This behaviour applies regardless of whether filters are selected within the same Tag Category or across multiple categories.

Product Tagging Considerations

Product tagging can also influence the results you see.

If a product contains multiple tags that correspond to different filters, it may appear in results even if it does not match all selected filters.

For example, a product tagged with both Blue and Large may appear when either filter is selected.

Summary

When multiple Tag Filters are selected on a storefront:

The filtering logic uses OR-based matching
Products that match any selected tag will appear in results
Results will not necessarily narrow to products matching all selected filters together

This behaviour is part of the current storefront filtering logic.

How do I Track Add-to-Cart Events and Marketing Tags in Infigo

This article answers common questions about implementing marketing tracking and verification tags on an Infigo storefront.

Specifically, it covers:

How to track Add-to-Cart clicks using Google Tag Manager
Why a TagServe tag may not fire
Why an Affiliate Window tag might fail
Where to add a Google Search Console verification tag

Because Infigo supports multiple product types and purchase flows, the implementation details may vary depending on how the storefront has been configured.

Tracking Add-to-Cart Clicks

In Infigo, there is no single universal Add-to-Cart button selector.

Different product flows use different buttons, meaning your tracking implementation may need to target multiple selectors.

Common examples include:

.nextStepButton
.productvariantaddtocartbutton
.multipartUi-V2-Footer button.button

These selectors correspond to different product types and checkout flows.

Important

These selectors are examples from common implementations.
Storefront templates and product flows can vary, so the exact selector required may differ between sites.

When configuring Google Tag Manager triggers, test your storefront to confirm which selector matches the Add-to-Cart button being used.

Tracking Add-to-Cart for MegaEdit Products

MegaEdit products may use a confirmation dialog when adding an item to the basket.

In these cases, the confirmation button may be targeted with a selector similar to:

div[aria-describedby="ngConfirmDialog"] .ui-dialog-buttonpane button:first-of-type

However, this selector may not work on every storefront, as MegaEdit implementations can differ depending on how the template is built.

If the confirmation button cannot be reliably targeted, a custom script or unique element identifier may be required.

Tracking Scripts Inside MegaEdit

In some storefront configurations, global tracking scripts added to the page header are not loaded inside MegaEdit editable content blocks.

If tracking is required within MegaEdit content:

the tracking snippet may need to be added directly inside the editable content block
this depends on how the MegaEdit template is implemented

TagServe Tags

If a storefront reports that a TagServe tag is not firing, note that TagServe is not recognised as a built-in feature within the Infigo platform.

To investigate further, gather additional information such as:

what system or platform the tag belongs to
how the tag was added (for example via GTM or custom script)
where the tag was implemented
any console or network errors

This information will help determine the cause of the issue.

Affiliate Window Tracking

Affiliate tracking platforms may use URL query parameters to identify referrals.

Example format:

?affiliateid=2

If an Affiliate Window tag is reported as failing, it is important to collect more details before investigation, such as:

the exact error or behaviour being observed
whether the affiliate parameter appears in the URL
how the affiliate tracking script has been implemented
any browser console or network errors

Some affiliate tracking implementations may require custom configuration or front-end development depending on the provider.

Google Search Console Verification

To verify ownership of a storefront in Google Search Console, a verification meta tag must be added to the site.

There are two common methods in Infigo.

Global verification

Add the verification meta tag to the page header container in Infigo settings.
This applies the verification tag across the entire storefront.

Page-specific verification

Verification tags can also be added through SEO settings within the Admin area for:

pages
categories
products
content pages

Please contact our support team for further assistance.

🚀 Storefront Configuration Problem Solvers 🚀

How Do I Enable Approval Navigation in the My Account Area?

Use cases

Key settings in the Platform

Step-by-step guide

Related links

How Do I Fix Incorrect Approval Email Links?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Fix Incorrect Out-of-Stock Messages?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Import Products with Images?

Use cases

Key settings in the system

Step-by-step guide

Related links

How Do I Resolve Sitemap URL and Namespace Errors?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Resolve the Invalid Platform URL Error?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Restrict Checkout to a Single Item?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Preselect a Specific Shipping Address at Checkout?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Fix Order Quantity Limit Errors?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Can I Force Confirm Deletion in Shopping Basket?

How Do I Configure a Discount Requirement on Basket Total?

Setup

Setting up the discount

How Do I Configure Storage Control Settings for Baskets / Carts and Saved Projects?

How Do I Configure MiniBasket for Accurate Line Item Count?

Use cases

Key settings in Infigo

Step-by-step guide

Related links

How Do I Add a Custom Binding to My Storefront?

Pre-Requisites

What We Need

The Process

How Do I Set Up and Use Reward Points on My Storefront?

Configuration

Enabling the feature

Configuration

How they work

How Do I Edit and Manage Customer Reward Points Adjustments on My Storefront?

2. Contents

3. Key Points and Takeaways

4. Key Settings

5. Scenario-Based Guide

Scenario 1: How to Edit Reward Points

Scenario 2: How to Delete Reward Points

Scenario 3: Auditing Reward Points Changes

6. FAQs

How do I Enable a Shipping-Specific Email Address for Storefront Orders Using the New “Contact Details for Order Notifications” Setting?

2. Contents

3. Key Points and Takeaways

4. Key Settings

Setting 1: Contact Details for Order Notifications

Setting 2: Address Email Address Required