Execute secondary store requests on cart abandonment
When a shopping cart is abandoned in Lightspeed Retail POS (X-Series), make a custom API request in Ingram Micro Cloud Marketplace to sync retargeting tags and customer deal flows.
See all Ingram Micro Cloud Marketplace + Lightspeed Retail POS (X-Series) integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Ingram Micro Cloud Marketplace Explore Ingram Micro Cloud Marketplace →
TriggersFires when a customer places a new order in Ingram Micro Cloud Marketplace.
Fires when an order in Ingram Micro Cloud Marketplace is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Ingram Micro Cloud Marketplace.
Fires when a customer abandons their cart before completing checkout in Ingram Micro Cloud Marketplace.
Creates or updates a product or listing in Ingram Micro Cloud Marketplace.
Updates an order's status or fulfillment details in Ingram Micro Cloud Marketplace.
Sends a custom API request to Ingram Micro Cloud Marketplace for actions not covered by a dedicated action.
Lightspeed Retail POS (X-Series) Explore Lightspeed Retail POS (X-Series) →
TriggersFires when a customer places a new order in Lightspeed Retail POS (X-Series).
Fires when an order in Lightspeed Retail POS (X-Series) is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Lightspeed Retail POS (X-Series).
Fires when a customer abandons their cart before completing checkout in Lightspeed Retail POS (X-Series).
Creates or updates a product or listing in Lightspeed Retail POS (X-Series).
Updates an order's status or fulfillment details in Lightspeed Retail POS (X-Series).
Sends a custom API request to Lightspeed Retail POS (X-Series) for actions not covered by a dedicated action.
More Ingram Micro Cloud Marketplace + Lightspeed Retail POS (X-Series) workflows
Sync newly approved affiliates across store locations
When a new affiliate is approved in Ingram Micro Cloud Marketplace, automatically send a custom API request to Lightspeed Retail POS (X-Series) so the affiliate account is mirrored in your second store.
See details
Cross-notify commission payouts between sales channels
Whenever an affiliate commission is earned in Ingram Micro Cloud Marketplace, execute a custom API call in Lightspeed Retail POS (X-Series) to update regional partner ledger metrics.
See details
See all Ingram Micro Cloud Marketplace + Lightspeed Retail POS (X-Series) integrations → · Browse the full workflow library →
Common questions
Can Knit build “Execute secondary store requests on cart abandonment” between Ingram Micro Cloud Marketplace and Lightspeed Retail POS (X-Series)?
Yes — describe it in the box above and Knit's Integrations Agent researches Ingram Micro Cloud Marketplace and Lightspeed Retail POS (X-Series)'s public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why connect two e-commerce apps like Ingram Micro Cloud Marketplace and Lightspeed Retail POS (X-Series)?
If you operate multi-channel storefronts, integrating Ingram Micro Cloud Marketplace and Lightspeed Retail POS (X-Series) keeps affiliate programs, commission tracking, and customer cart updates synchronized across both systems.
How do custom API requests work between Ingram Micro Cloud Marketplace and Lightspeed Retail POS (X-Series)?
Events like abandoned carts or approved affiliates in Ingram Micro Cloud Marketplace can automatically issue custom API requests to Lightspeed Retail POS (X-Series) to ensure equal data representation.