Pyle

ERP Bridge ​

What This Is ​

ERP Bridge is the admin review surface your team uses to inspect ERP sync traffic and retry failed or incomplete sync requests when the shared package exposes enough context to do so.

In the inspected shared package, this lives under Settings > Erp Bridge.

When You Would Use It ​

Use ERP Bridge when you need to:

  • check whether a sync request reached the ERP
  • review the endpoint and HTTP result of a sync attempt
  • inspect exception messages on failed ERP requests
  • retry a sync from the request log when the row supports it

This is not the place where you edit products, customers, or orders themselves. It is a review and troubleshooting surface for integration traffic.

Before You Start ​

Make sure:

  • you have access to the admin settings area
  • you know which model or sync flow you are investigating
  • you understand that the packaged page is request-log oriented, not a full ERP connector setup console

How To Use It In The Admin ​

  1. Open Settings > Erp Bridge.
  2. Search for the request you care about by endpoint, external ID, or exception detail if your project indexed that data.
  3. Review the main columns first:
    • created time
    • HTTP method
    • endpoint
    • response HTTP code
    • exception message
    • exception HTTP code
  4. Open the row action menu.
  5. If Retry sync is available, use it only when you are confident the underlying data issue has been fixed or the request is safe to replay.
  6. Re-check the log table after the retry.

What It Changes In The Product ​

ERP Bridge review does not change business records by itself.

The only direct packaged operator action in this pass is retrying an eligible sync request. When that succeeds, the downstream business record may update as part of the ERP sync flow.

Common Tasks ​

  • confirm that a sync request was sent
  • check whether the ERP returned an error
  • identify the endpoint or sync class involved in a failure
  • retry a request after fixing the root cause

Rules, Limits, And Things To Watch ​

  • The packaged page is a request-log screen, not a full mapping or credentials screen.
  • Retry sync is only available on rows that can actually be replayed.
  • ERP request logs are not the same thing as business activity logs.
  • Some ERP behavior still depends on host-app connector configuration outside the shared framework package.

Troubleshooting ​

The row shows an exception ​

Start with the exception message and HTTP code. Those are the fastest clues about whether the problem is authentication, payload shape, missing data, or a remote-system issue.

Retry sync is disabled ​

That usually means the log row does not have enough context to replay the sync.

The business record still looks wrong ​

The ERP Bridge page only shows request history. If the request succeeded, inspect the actual business record and its sync path next.

For the full operator recovery checklist, see How to troubleshoot a failed ERP sync.

Sources ​

  • packages/admin/routes/web.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/Page.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/DataTable.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/DataTable/Row/ActionsMenu.php
  • packages/admin/resources/views/components/settings/erp-bridge/data-table.blade.php
  • packages/erp-bridge/src/Models/RequestLog.php
  • packages/framework/src/Services/ErpBridge/AbstractErpSyncService.php