Integration logs

Integration logs for every connection in one place

Integration logs and API integration monitoring: track webhooks, inspect sync errors and monitor system events in real time.

In short

Integration logs in StoreChart record every webhook, sync run, shipping-carrier call and sales-channel event, with its status, store and error details. You can filter by status, category and store, and search the messages. A failed WooCommerce, Shopify or custom webhook raises a high-priority in-app notification, while other failures wait in the log.

One log for every connection

Every webhook, sync and error, with the details to check

  • One log for WooCommerce and Shopify webhooks and sync, inbound webhooks, shipping integrations and sales-channel events
  • A high-priority in-app notification when a WooCommerce, Shopify or custom webhook fails
  • Filter by status, success, error or info, and by category, store and import source
  • Search across event types, messages and store names
  • Each entry keeps its details, such as the payload and error message, for troubleshooting

Integration log features

Every connection failure is recorded for review

Unified event log
Webhooks received, sync runs, shipping-integration calls and sales-channel events, every entry tagged with its store, category and status.
Failure alerts
A failed WooCommerce, Shopify or custom webhook, and a sync in which orders failed to come in, create a high-priority notification in the bell.
Status filters
Show only errors, only successes or only informational events, and narrow down by category and import source.
Per-store view
The global store selector limits the log to one store, or shows every store together.
Search
Find an entry by event type, message text or store name, for example, every entry that mentions a specific order number.
Retention, cleanup and export
Older entries are cleaned up automatically, and you can export the log to a JSON file or clear it yourself whenever you want a fresh start.

Using the log in 3 steps

From "maybe something broke" to a clear answer

1
Connect your integrations

Connect WooCommerce, Shopify, shipping or sales channels. Their events start appearing in the log automatically: there is nothing to enable.

2
Failure notifications

A failed webhook creates a high-priority in-app notification, and other failures wait in the log under the error filter.

3
Filter and search

Filter by status, category and store, search the messages, and open the entry to see what went wrong.

Integration logs: finding sync failures

What the log records

Integration logs show what your store's connections did while you weren't looking. Three sources write to them:

  • Store connections: WooCommerce, Shopify and custom connections record every webhook received and every sync run.
  • Shipping: each order sent to the carrier, the tracking number, and the request and response when something failed.
  • Sales channels: events such as an order coming in from a partner's storefront.

Entries are written automatically from the moment a connection is live, with nothing to set up.

Status, category and search

Every entry is tagged with its store, status and category. Combining them narrows hundreds of entries down to the few that matter right now.

  • Status: for example success, info, warning, error or processing.
  • Category: webhook, sync, connection, shipping or sales channel.
  • Store: the global selector shows one store or all of them.
  • Search: by event type, message text or store name.

Tracking down a sync failure

  1. Pick a store and choose the error status.
  2. If needed, narrow it to one category.
  3. Search for an order number, an event name or a word from the error message.
  4. Open the entry to see the details that were saved.
  5. After the fix, check that new entries arrive with a success status.

One error among dozens of successes usually points to an order with an unusual value. If every webhook from one store has failed since the same hour, something probably changed in the connection, such as a revoked API key.

When the bell alerts you

Not every error reaches the bell:

  • Failed webhook: from WooCommerce, Shopify or a custom connection, creates a high-priority notification.
  • Partial sync: a sync in which orders failed to come in arrives at high priority.
  • Shipping: a failed shipment to a carrier is logged without a notification.
  • Sales channels: a failed event is logged without a notification.

So it's worth opening the log with the error filter once a day. Whoever owns the connections should also make sure the operations category isn't muted for them.

Example: orders that never reached the courier

Illustrative only. A Shopify store sends about 60 orders a day to a courier through StoreChart. A customer asks why she has no tracking number, and the bell is empty.

  1. Filter by the shipping category and error status: 9 entries from that morning.
  2. All of them carry the same message about an incomplete address.
  3. The request saved in each entry shows the house number was typed into another field.
  4. The team fixes the addresses and handles the orders.
  5. They export the entries to a JSON file, in case the problem comes back.

From that day on, a midday error check becomes part of the team's routine.

Who it's for and what's not included

  • Good fit: a store connected to WooCommerce or Shopify that ships through the system or runs sales channels.
  • Sharing with support: copy the event type, time and error message, and send them to the support team or the integration provider.
  • Retention: only the most recent entries are kept, and older ones are deleted automatically. It isn't an archive.
  • Export and clear: export to a JSON file before entries are cleaned up, and clear the log by hand whenever you want.
  • External monitoring: no forwarding to a monitoring system and no outgoing webhooks.
  • Alert rules: no rules you define yourself.

Key integrations

Questions about integration logs

Why do I need logs if everything is working?

Because problems start silently: one failed webhook can turn into several unsynced orders. With the log and failure notifications, you notice the issue early, not after a customer complains.

How long is log history retained?

The log keeps the most recent events for each account, and older entries are cleaned up automatically to keep it fast. It is built for troubleshooting current issues rather than long-term archiving.

What happens when a webhook fails?

When a WooCommerce, Shopify or custom webhook fails, the failure is recorded in the log with its error message and details, and a high-priority in-app notification is created. WooCommerce and Shopify apply their own redelivery rules to webhooks that don't receive a success response.

Can I filter logs by a specific store?

Yes. Every entry is tagged with its store and category, and the global store selector limits the log to one store. Combine it with the status filter to see, for example, only the errors for Store A.

What does an entry for a shipment sent to a carrier show?

The order, the carrier and the tracking number if one came back, along with the request that was sent and the response that returned. If the shipment failed, you also see the error details. A failure like that is recorded in the log but doesn't create a notification in the bell.

How can I share a log entry with the support team?

Find the entry with the filters or search, then export the log to a JSON file or copy the event type, time and error message. Send that to the support team or the integration provider, which is usually enough to pinpoint the issue.

Do I get alerted the moment an integration event fails?

Not for every failure. A failed WooCommerce, Shopify or custom webhook, and a sync in which orders failed to come in, create a high-priority notification. Shipping and sales-channel failures are recorded in the log without a notification, so it pays to filter by errors regularly.

Every sync failure in plain sight

One log with failure alerts, filters and search for every connection