Custom commerce integrations
Use a prepared custom commerce integration when your website needs store-specific product, customer or order behaviour.
What it is
Custom Script lets INSIDE use a prepared integration for a store with website-specific behaviour. It can supply the product, customer and order operations that the integration implements. You select the integration in Commerce Providers.
Who uses it and why
Administrators with Settings or Developer select a prepared integration and decide where it applies. Developers define the store information and verification behaviour needed with Powerfront. Operators use the resulting commerce screens without configuring the integration itself.
Where to find it
Open Settings › Commerce › Commerce Providers. Choose Custom Script as Provider type, then select an available Custom Script. Configuration needs Settings with the relevant AI access, or Developer.
How it works
The custom integration supplies its supported operations to INSIDE. These can include product search, product filters, product lookup, customer lookup, customer search, order search, order lists and order lookup.
INSIDE applies the same provider selection rules as for native stores. Returned products and records use shared commerce cards and identifiers. Search filters depend on the capabilities declared by the custom integration.
Visitor access needs additional verification behaviour. The integration must check store sign-in evidence or exact order details and confirm ownership before private information can be disclosed. Supplying a customer identifier alone does not prove identity.
Configure it
Ask Powerfront to prepare or update the custom integration. Agree its supported operations, credential setup, search filters and any visitor verification or basket behaviour. These details vary by integration.
Create a Commerce Provider, select the prepared Custom Script, choose at least one supported operation under Use for, and set Availability. Save and use test to check availability. Check the actual store operations with representative records as part of the integration setup.
Configure Customer and order access only when the integration supplies the corresponding verification support. Product panel replacement is also a separate choice.
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| Custom Script | Settings › Commerce › Commerce Providers | Yes | Selects a prepared commerce integration available to this website. |
Permissions
| Permission | Lets you |
|---|---|
| Settings | Select a custom provider and its operations, subject to AI access and View Only. |
| AI | Allows commerce administration for a restricted Settings role. |
| Developer | Configure the custom commerce provider. |
Limits and good to know
- Selecting an operation does not create its implementation. Missing support produces an unsupported-operation result.
- Structured private search filters must be declared by the integration. Arbitrary filters are not accepted by default.
- Custom integrations do not share a universal credentials form or default settings.
- Guest order verification and store sign-in can have different availability.
- Basket support is not implied by catalogue support.
Depends on and works with
+1 more · this feature uses
- Custom scripts managed by PowerfrontRequires
Powerfront must deploy an available custom commerce script before it can be selected as a provider.
View all connections as a list
This feature uses
- Roles and permissionsConfigured by
Roles control provider administration.
- Commerce provider setup and selectionRequires
Custom providers use the shared enabled operations, availability and routing rules.
- Product search and filtersEnhances
A custom integration can supply product search and declared filters.
- Product options and variant selectionEnhances
A custom integration can supply product lookup, options and variants.
- Store customer matches and ordersEnhances
Implemented customer lookup and order list operations can supply the CRM panel.
- AI customer and order searchEnhances
Implemented private search operations can be exposed to authenticated operator Team Chat.
- Customer and order accessConfigured by
Visitor access requires implemented verification and ownership checks as well as the access policy.
- Store order details and historyEnhances
Implemented order reads can supply order details and customer history.
- Custom scripts managed by PowerfrontRequires
Powerfront must deploy an available custom commerce script before it can be selected as a provider.
Used by
- Commerce provider setup and selectionEnhances
Supplies website-specific Custom Script providers.
- Product search and filtersEnhances
A custom provider can supply implemented search and filters.
- Product options and variant selectionEnhances
A custom integration can supply supported product detail operations.
- Store customer matches and ordersEnhances
A custom provider can implement the panel's required operations.
- AI customer and order searchEnhances
Custom providers can implement private search and declare supported filters.
- Customer and order accessEnhances
A custom provider can supply supported verification methods.
- Store order details and historyEnhances
Custom providers can supply customer and order reads.
- Service customisation support · managed by PowerfrontRelated
Custom commerce integrations provide a dedicated setup for store-specific service behaviour.
FAQ and troubleshooting
Why is my custom integration missing from the list?
Ask Powerfront to check that the prepared commerce integration is available to this website.
Why does a selected operation fail?
The integration must implement that operation and be able to reach its store. Ask Powerfront to check the integration's supported operations and credentials.
Why is a search filter rejected?
The integration must explicitly support the filter. Use a supported criterion or ask Powerfront to extend the integration.
Can I enable visitor order access for any custom provider?
Only if it implements the required verification and ownership checks. Private operator access does not provide visitor verification.