Extensibility
Extend Comarch customer and store mapping with connector script hooks.
The default mapping covers the common loyalty fields. Extensibility is useful when a project needs extra Comarch attributes or a different pass payload shape.
Where custom mapping is configured
Custom mapping is configured in the Advanced tab of the Comarch settings editor.
This is where connector scripts can be added to extend or override the default customer and store mapping.
The Wallet Crew support can be contacted when custom mapping needs to be configured or reviewed.
Available hooks
The connector exposes two script hooks.
extensions.comarch.customerMapper
Extend or override customer mapping
After customer data is fetched and the standard mapping is applied
extensions.comarch.locationMapper
Extend or override store mapping
After store data is fetched and the standard mapping is applied
When to use extensibility
Use a custom hook when the pass needs data that is not mapped by default.
Common cases include custom profile attributes, loyalty labels, extra location metadata, or project-specific field names.
What the hooks receive
Each hook receives the raw Comarch response and the pass entity.
This makes it possible to reuse any field present in the source payload, not only the default mapped fields.
The raw objects are also exposed for inspection under:
debug.comarch.customerdebug.comarch.store
Recommended approach
Start with the default mapping first.
Then add only the extra fields that the pass really needs. This keeps templates simpler and reduces long-term maintenance.
Safety notes
Apply mapping changes in staging first.
A mapping script can affect every pass refresh that uses the connector. Validation should cover both data correctness and template rendering.
FAQ
Where is custom Comarch mapping configured?
Custom mapping is configured in the Advanced tab of the Comarch settings editor.
This is where connector scripts can be added to extend or override the default mapping.
Last updated