Overview
The Commerce Connector with real‑time, multi‑step data exchange capabilities enables organizations to build flexible, event‑driven, and callback‑based integrations with external systems such as ERPs, pricing engines, inventory systems, and file‑based platforms.
This feature includes:
- Multi‑step integration pipelines
- Real‑time event triggering
- Real‑time storefront callbacks
- HTTP‑based execution framework
- Backward compatibility with existing scheduled exchanges
These capabilities allow Znode to automatically react to business events, retrieve live data during storefront requests, and orchestrate complex workflows across APIs, SFTP, and Blob Storage.
Key Features
Multi‑Step Data Exchanges
Data Exchanges support unlimited sequential steps.
Capabilities
- Add unlimited integration steps
- Execute steps sequentially
- Configure an independent mapper per step
- Reuse data from previous steps
- Apply transformations only where required
- Reference prior step outputs using step prefixes
Example
Step1.Account.Name
Step2.SalesOrderNumber
Supported Transmission Modes
| Mode | Usage |
|---|---|
| API | Real‑time and lightweight integrations |
| SFTP | Legacy ERP file‑based integrations |
| Blob Storage | Large file exchanges |
| Import Handler | Bulk Znode imports |
Trigger Execution Framework (HTTP)
- A new Trigger Execution (HTTP) section is available in Manage Data Exchange.
- Trigger Execution must be enabled for all multi‑step exchanges.
- Supported trigger types:
- Znode Event (Push Model)
- Znode Callback (Pull Model)
Real‑Time Execution Models
Znode Event – Push‑Based Execution
Automatically executes a Data Exchange when a configured Znode system event occurs.
Supported Event Modules
- Account
- Order
- Product
- Category
- Price
- Inventory
- Catalog
- Portal
Typical Events
- Account Updated
- Order Created
- Product Changed
Example Use Case
Account Updated → Fetch Account Details → Transform Data → Send to ERP or SFTP
Znode Callback – Pull‑Based Execution
Retrieves live pricing or inventory data from external systems during storefront requests.
Supported Callback Types
- Real‑time Pricing
- Real‑time Inventory
Supported Storefront Scenarios
- Real‑time pricing on Product Detail Page (PDP)
- Real‑time inventory availability
Callback Behaviour
- Shopper initiates storefront request
- Znode triggers callback
- Commerce Connector calls external API
- Response is transformed using Global Mapper
- Live data is returned to the storefront
Required Global Mapper Fields
- Sales Price
- Retail Price
- SKU
- Line-Item ID
When to Use Event‑Based vs API‑Based Execution
| Criteria | Event‑Based | API‑Based |
|---|---|---|
| When to Use | When event exists in Znode | When event does not exist |
| Trigger | Automatic system event | Manual API invocation |
| Dependency | Znode events | External system |
| Control | Limited | High |
| Use Cases | Order Created, Registration | Custom workflows |
Configuration: Event‑Based Real‑time Execution
Prerequisites
- Administrator access
- Commerce Connector enabled
- Events configured
- External APIs reachable
Steps
- Navigate to Commerce Connector
- Create Data Exchange
- Enable Trigger Execution
- Select Event
- View Event Payload
- Understand Step 0 (read‑only event payload)
- Configure Return Payload option
- Configure Processing Steps
- Configure API Request
- Map Data Between Steps
Step2.SalesOrderName : Step0.Payload.EventDataCode
Workflow
- Znode event occurs
- Trigger validation executes
- Data exchange starts
- Steps execute sequentially
- Data is transformed
- Operations execute
- Status logged
Callback Configuration
- Enable Znode Callback trigger
- Select action (e.g. Real‑Time Inventory)
- Configure ERP steps
Global Mapper
Executes after all steps and formats final response.
Must use next step prefix.
Step2.QuantityAvailable : Step1.InventoryQuantity
Step2.SKU : Step1.ProductSKU
Execution Flow Summary
- Shopper opens PDP
- Callback triggered
- Steps execute
- ERP called
- Global mapper formats data
- Live data returned
Best Practices
- Enable callbacks
- Disable legacy integrations
- Keep APIs fast
- Use caching
Use Cases
Real‑Time Order Creation
- Trigger: Order Created
- Steps process header and lines
- ERP API called
Real‑Time Pricing
- Trigger: PDP load
- API call returns price
Account Updates
- Trigger: Account Updated
- Syncs with ERP
Multi‑Step Enrichment
- Tax API
- Shipping API
- Data combined
Backward Compatibility
- Existing schedulers continue
- No migration required
Limitations
- No advanced monitoring
- No retry UI
- No custom processors
Performance Recommendations
- Response < 2 seconds
- Payload < 1 MB
- ERP latency < 500 ms
Summary
Znode’s real‑time, multi‑step data exchange framework enables event‑driven automation, live data retrieval, and scalable integrations while maintaining backward compatibility.