How Neto E-Commerce Integration Works

Source: neto_controller.rb

• Authentication is skipped if a valid token already exists on the company record, preventing redundant OAuth flows
• After successful authentication, the user is redirected to the Neto settings page for configuration
• Unauthorising (disconnecting) Neto clears ALL Neto-related fields plus the warehouse setting from the company record — this is a complete wipe with no undo
• The unauthorise endpoint can find the integration by store_id, allowing external callback-driven disconnection

Support scenarios

• "We disconnected Neto and lost all our settings" → Unauthorising Neto performs a complete wipe of all Neto fields including the warehouse setting. This cannot be undone through the UI — all settings need to be reconfigured if the workshop reconnects.
• "Neto auth keeps redirecting but nothing happens" → If a token already exists, auth is skipped. If the existing token is invalid or expired, the system may skip auth but then fail on API calls. Try clearing the existing token first, then re-authenticate.
• "Neto disconnected itself without us doing anything" → The unauthorise endpoint can be triggered by external callbacks using the store_id. Check if Neto sent a disconnection callback, which would have cleared all fields automatically.