Skip to main content

How to use system logs

The Logs section provides a detailed audit trail of all communication between StoreLinkr and your connected sales channels, suppliers, and external APIs. This is the first place you should look if data isn't syncing as expected.

Monitoring Communication​

Navigate to Settings > Logs to see a list of recent API requests and responses. Each log entry includes:

  • Status Code:
    • OK (200-208): The request was successful.
    • Warning (300-499): There was an issue with the request (e.g., "Not Found" or "Unauthorized").
    • Error (500+): The external system encountered a server-side problem.
  • Action: What was being done (e.g., CREATE_PRODUCT, UPDATE_STOCK, IMPORT_ORDER).
  • Integration: Which platform was involved (e.g., Bol.com, Shopify, or a specific supplier).
  • Time: How long the request took to process.

Deep Diving into Issues​

Click on any log entry to open the Log Details modal. From here, you can see the technical details:

  1. URL & Method: The exact API endpoint that was called.
  2. Request Body: The data that StoreLinkr sent.
  3. Response Body: The raw answer from the external system. This often contains the specific reason why a sync failed.
  4. Error Message: A human-readable summary of any problems encountered.

Linking to Products​

If a log entry is related to a specific product action (like failing to update a price), you'll often see a View Product button in the details modal. This allows you to jump directly to the item in the PIM to fix data quality issues.

Filtering Logs​

Use the filters at the top to narrow down your investigation:

  • Status Code: Focus only on "Error" or "Warning" logs.
  • Integration: See logs for a specific marketplace or online store only.
tip

Regularly monitoring your logs helps you identify and fix integration issues before they impact your sales or inventory accuracy.