Lightweight integration without importing orders

RetJet doesn’t create a copy of your order database and doesn’t fetch data “just in case”. Details of a specific order are fetched through the API only when a return request comes in, or when a member of staff needs to verify something. That means your store’s system isn’t burdened unnecessarily, and setup stays simple and safe.

How it works

• A request or an action in the dashboard triggers a one-off call to the store for the data needed to handle that specific case.
• Once a decision is made (e.g. a refund), RetJet sends the store the outcome and the case status.
• There’s no constant, full sync of every order. Only the data needed at that moment is exchanged.

What the store gains

• Lighter load on your systems and a shorter setup time.
• Fewer points of failure, since there’s no continuous exchange of large chunks of data.
• Easier compliance with data minimization rules.

Example

The customer submits a request. RetJet fetches only the data for that one order, and sends back the outcome once a decision is made. No other orders are fetched or stored.