What's New in Infigo | October 2025

A new MegaScripts-based integration connects Infigo storefronts with HubSpot CRM.
Customer and order data can now sync automatically, creating or updating HubSpot contacts and deals when orders are placed—enabling sales teams to track order progress in real time.

Highlights

• Syncs customers, orders, and deals to HubSpot CRM

• Uses pipelines and affiliate data for record linking

• Automates contact and order creation

• Built on configurable MegaScripts for flexibility

How to implement

1. Create a new MegaScript and configure it to trigger on Place Order.

2. Include HubSpot connection details such as pipeline, deal stage, and associations.

3. Link the MegaScript to your storefront under Connect: Scripting.

4. Place an order and verify that corresponding contacts and deals are created in HubSpot.

A new appearance setting updates the behaviour of Login Style “Option 2 (Recommended for B2B)”, keeping the background image fixed while only the form scrolls.
This provides a sleeker, more professional look for corporate storefronts and ensures consistent branding across devices.

Highlights

• Added appearance setting for controlled scroll behaviour

• Background image remains static as the form moves

• Optimised for B2B login experiences

How to implement

1. Go to Admin > Appearance Settings.

2. Select Login Style: Option 2 (Recommended for B2B).

3. Enable the new “Fixed background scroll” setting.

4. Save and preview the login page to confirm only the form scrolls.

Administrators now have fine-grained control over whether customers must enter a first and/or last name when registering or updating their account.
This helps storefronts adapt to different market needs, such as B2B sites where company data is the priority or B2C sites that require full personal details.

Highlights

• Four new settings: first/last name enabled and required
  
• Applies on registration and “My Account” pages
  
• Simplifies compliance with varied onboarding policies
  
• Reduces friction for corporate or anonymous-checkout workflows
  

How to implement

1. Go to Admin > Settings > Customer Settings.
   
2. Enable or disable the options for First Name and Last Name (both Enabled and Required states).
   

Save changes and test on the storefront registration and “My Account” pages.

Administrators now have fine-grained control over whether customers must enter a first and/or last name when registering or updating their account.
This helps storefronts adapt to different market needs, such as B2B sites where company data is the priority or B2C sites that require full personal details.

A new notification feature automatically emails designated users when the CERM MIS server cannot be reached.
This ensures that technical teams are immediately aware of integration or network problems, minimising downtime for automated workflows.

Highlights

• New message template and tokens for CERM alerts

• Detects server or connectivity failures

• Supports proactive maintenance and monitoring

How to implement

1. Go to Admin > Message Templates and locate the new CERM Connectivity Alert template.

2. Configure the email recipients and customise the message body.

3. Ensure the CERM plugin is enabled and connected.

4. Simulate a connection loss (if safe to do so) to confirm alerts are triggered.

Storefronts integrated with CERM can now choose whether Infigo should enforce the Payment Manner set in CERM or use native payment-method rules instead.
This allows administrators to bypass CERM’s payment-manner logic where local payment gateways or methods differ from those in MIS.

Highlights

• New CERM setting “Payment Methods Control Property”

• Options: Payment Manner (existing) or None (native control)

• Enables hybrid checkout/payment configurations

• Reduces integration friction for diverse payment setups

How to implement

1. Go to Connect: CERM > Settings.

2. Locate the new Payment Methods Control Property option.

3. Choose Payment Manner (CERM-controlled) or None (Infigo-controlled).

4. Test checkout to confirm correct payment method visibility.

   

Several improvements were made to strengthen the CERM integration and user communication.
New message templates handle MIS-plugin responses, order summaries are now editable via content items, and additional CERM settings expand product-deletion and thumbnail options.

Highlights

• Three new message templates for CERM events

• Editable section added to order summary page

• New settings: Allow delete products/estimates and Fallback to Master Product Thumbnail

• Improved order-confirmation logic and email handling

How to implement

1. Go to Connect: CERM > Settings to review new options.

2. In Message Templates, configure the new CERM Success, Failed, and Partial Success templates.

3. Verify editable content on the Order Summary page now matches previous layout and tokens.

4. Test by placing and completing an order to confirm correct email notifications.

Infigo now supports automatic translation of PitStop XML text—including Hebrew characters—within PDF profile reports.
This enhancement improves global usability and ensures that error and pre-flight details appear correctly in localized scripts.

Highlights

• Added multi-language translation for XML text

• Hebrew fully supported in PitStop reports

• Controlled via a new setting in PDF Profile Settings

• Requires API key for translation activation

How to implement

1. Go to Admin > PDF Profiles > Profile Settings.

2. Enable the new option for XML Translation Support.

3. Enter a valid API key if translation services are required.

4. Generate a PitStop XML report to verify translated text displays correctly.

The file-upload area for downloadable products has been redesigned for clarity and consistency.
Managers can now clearly see file name, size, and available actions after saving or refreshing, making it easier to manage digital assets.

Highlights

• Refreshed UI shows file name and size after save/refresh

• Upload, download, and remove actions always visible

• Backend auditing shows filename and size on edit

How to implement

1. Go to Admin > Catalog > Products and edit a downloadable product.

2. In the Product Variant > Downloadable Files section, upload a new file.

3. Save and refresh to confirm file details display (name, size, and action buttons).

A new UI control makes managing PDF Profile variables much easier.
Instead of editing XML manually, administrators can use a simple on-screen editor that automatically validates XML when switching between modes.

Highlights

• New variable-set editor within the PDF Profile page

• Supports both Simple (UI) and Advanced (XML) modes

• Built-in XML validation for error prevention

• Streamlines workflow for non-technical users

How to implement

1. Go to Admin > PDF Profiles and open a profile for editing.

2. Switch between Simple (UI mapping) and Advanced (manual XML) modes.

3. In Simple mode, map variables to product attributes, specification attributes, quantity, or constants.

4. Save the profile and test with a sample product to ensure values map correctly.

Multipart preview generation can now use specific PDF page boxes—such as TrimBox, CropBox, BleedBox, or ArtBox—instead of always defaulting to MediaBox.
This gives production teams precise control over how artwork is rendered for proofing.

Highlights

• Select which page box defines the preview area

• Supports TrimBox, CropBox, BleedBox, ArtBox

• Default remains MediaBox for backwards compatibility

How to implement

1. Edit a multipart product in Admin > Products.

2. In the multipart configuration XML, set previewPageBoxOption to the desired value (e.g. TrimBox).

3. Save and preview the product to confirm the selected box is used for image generation.

When tiered pricing is active, attribute value lists now display tier information directly, improving transparency for storefront admins.

Highlights

• Attribute editor now shows tier levels and prices

• Simplifies configuration of quantity-based discounts

• Reduces need to cross-reference pricing tables

How to implement

1. Go to Admin > Catalog > Attributes > Product Attributes.

2. Edit or create an attribute with tier pricing enabled.

3. Use the Value Editor to define price tiers (absolute or percentage).

4. Assign the attribute to a product or group and verify tier display in both Admin and storefront views.

A new configuration allows departments to manage all addresses centrally.
When “Use department address exclusively” is enabled, customer addresses are replaced with department-level ones across checkout and My Account.
Split-shipping and VAT logic have been updated to support this mode.

Highlights

• Centralised address control per department

• Department address replaces individual customer ones

• Fully supported in checkout and split shipping

• Simplifies administration for enterprise accounts

How to implement

1. Go to Admin > Departments > Edit Department.

2. Enable the setting Use department address exclusively.

3. Test by checking address management in My Account and during Checkout—only department addresses should appear.

Departments can now automatically use their own address as the billing address during checkout.
This eliminates redundant entry steps for corporate users and ensures that financial documentation always matches departmental billing data.

Highlights

• New setting “Use department address as billing address”

• Skips billing-address step at checkout

• Makes address fields read-only when active

• Ensures consistency in My Account and Admin views

How to implement

1. Go to Admin > Departments > Edit Department.

2. Enable Use department address as billing address.

3. Confirm that during checkout, the billing address step is skipped for users linked to that department.

4. Verify that address fields in My Account and Admin are read-only.

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

1. Go to Admin > Configuration > Email Accounts.

2. Edit an existing email account or create a new one.

3. Select OAuth 2.0 Authentication and enter the required credentials.

4. Send a test email to confirm token-based authentication works.

MegaScripts can now place orders directly from HTML forms—no login or checkout required.
This opens powerful new workflow options for sample requests, internal ordering, or marketing campaign forms that feed directly into production.

Highlights

• Forms can create orders via API without checkout

• Field mapping links form inputs to order models

• Supports configurable success/error pages

• Enables custom web-to-print forms and landing pages

How to implement

1. Create or edit a MegaScript with a trigger on Form Submit or Place Order.

2. Define variable mappings in the script configuration (e.g. ${email}, ${first_name}).

3. Attach the MegaScript to your storefront through Connect: Scripting.

4. Build a web form and test by submitting an order to verify it appears in Admin.

A new basket option allows customers to edit quantities for versioned multipart products directly in the cart.
This simplifies order management for complex multi-version products.

Highlights

• New basket setting “Allow quantity editing for versions”

• Enables inline quantity adjustments for multipart items

• Reduces checkout friction for high-volume users

How to implement

1. Go to Admin > Basket Settings.

2. Enable Allow quantity editing for versions.

3. If needed, enable Consider versions on min/max quantity checks for correct validation.

4. Test by adding a versioned product to the basket and adjusting quantities.

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

1. Go to Admin > Languages.

2. Edit the desired language and search for keys vue.datepicker.days and vue.datepicker.months.

3. Update the comma-separated values for days (7) and months (12).

4. Save and verify translations appear in the storefront datepicker.