RetJet does not create a copy of your order database and does not prefetch data. Details for a specific order are fetched via API only when needed – for example, when a return request is created or when a staff member needs to verify details. This keeps the store’s systems from being unnecessarily loaded and makes the rollout simple and safe.

How it works

• A return request or an action in the panel triggers a one-time API call to fetch just the data required for that case.
• After a decision is made (e.g., refund), RetJet sends the outcome and updated status back to the store.
• There is no constant, full synchronization of all orders. Only the data needed at that moment is transferred.

What the store gains

• Lower system load and faster implementation.
• Fewer failure points, since there’s no continuous exchange of large data sets.
• Easier data-minimization compliance, because only necessary data is processed.

Example
A customer submits a return request. RetJet fetches data only for that order, processes the case, and then sends the result back to the store. No other orders are fetched or stored.