What's New in Infigo | August 2025

Launching a new storefront just got a lot faster. You can now copy products directly from one storefront to another from the Product management grid. This saves time, removes repetitive build steps, and helps you keep catalogs consistent across multiple stores.

From the grid, select one or many products and choose Copy products to open a guided dialog. Pick the destination storefront, decide whether the copied items should be published, and set the naming: for a single product you choose the exact name; for multiple products you provide a prefix that’s added to each copy. The copy runs as a background job, so you can carry on working while it completes.

This initial release focuses on the most common workflows. Today, selection from the grid supports up to 500 products at a time; if you need more, filter and repeat. Copies run one source store → one destination per run (repeat the action to place the same product on additional storefronts). A short walkthrough video is linked from the companion page for a full demo.

Highlights

• Available to all admin users by default

• Copy one or many products from the Product management grid

• Choose a destination storefront before starting the copy

• Enter an exact name for singles or a prefix for multiples

• Background processing with an option to publish on creation

How to implement

1. Go to Admin → Product management in the source storefront.

2. Filter or search as needed, then tick the checkbox(es) for the product(s) you want to copy.

3. Click Copy products to open the copy dialog.

4. Select the destination storefront.

5. For a single product, enter the new product name; for multiple, enter a name prefix.

6. Choose whether the copied product(s) should be published.

7. Click Copy product(s) to queue the job.

8. When processing completes, open Product management on the destination storefront and search for the new name/prefix to confirm the copies.

A new “Create an order” MegaScript pattern accepts payloads from a simple hosted form or a Trigger URL. It validates inputs, can create (or re-use) the customer, and records an order with predefined products, quantities and delivery options.

This is particularly handy for events, kiosks or lightweight portals. HTML responses (via editable content) or JSON are both supported.

Highlights

• Works with a hosted form or a Trigger URL

• Supports defaults and content overrides

• Can auto-create customers when needed

• Optional one-order-only restriction per email

• Returns HTML (content keys) or JSON for custom handlers

How to implement

1. Configure the payload (line items, defaults, log level)

2. Copy the Trigger URL from Admin

3. (Optional) Add editable content keys for success/error HTML

4. Embed the provided fetch example (replace with your Trigger URL)

5. Set createCustomerIfNotExists: true to auto-create, and allowMultipleOrders: false to limit to one order

Insights has been extended with request-context details (e.g., context name) to improve filtering and grouping. A helper dashboard has been added to demonstrate the new columns.

Highlights

• Adds request-context metadata to reporting tables

• Enables richer filtering and grouping in dashboards

• Companion dashboard provided for quick validation

From the Customer record, you can now open Message Queue pre-filtered to that customer. This shortens the path to review communications history for support or account management.

The link appears directly within the customer details experience, saving you from manual filtering.

Highlights

• “Related messages” link from the customer record

• Opens Message Queue with the customer filter applied

• Speeds up comms triage for support teams

Setting up payment gateways is now simpler and more fool-proof thanks to a review and refinement of our payment-plugins. Configuration screens across multiple gateway plugins have been updated to provide clearer tool-tips, up-to-date field descriptions and a more consistent layout, so administrators can integrate providers quickly and confidently, with far less trial-and-error.

Highlights

• Clearer configuration pages – many payment plugin now shows helpful guidance for each setting, so you know exactly what information is required.

• Current-API credential handling – numerous plugins have been aligned with the latest authentication flows used by their respective providers, reducing the risk of connectivity errors.

• UI consistency – improved styling and layout bring payment-gateway setup pages into line, making administration more intuitive.

• Under-the-hood code review – extensive cleanup and best-practice updates increase reliability, security and long-term maintainability.

By keeping gateway plugins modern and easy to configure, these enhancements translate directly into smoother, more dependable checkout experiences for your customers.

Take a look at the new tutorials added to the Infigo Academy over the last month and keep your skills sharp!