Ensuring a seamless flow of data between your sales channels and Logiwa IO is critical for efficient fulfillment. When an order fails to download or a product fails to sync, it can cause significant operational delays and customer dissatisfaction. To provide clear and immediate insight into these issues, we have introduced the
Integration Monitoring module.
This centralized dashboard is designed to act as your primary tool for overseeing the health of your integrations. Instead of manually searching through logs to diagnose a problem, you can use this screen to proactively identify and resolve potential issues.
The Integration Monitoring module, located under the Integrations menu, includes a tab called Items for Review. This tab is divided into four sections, each providing specific insights into different aspects of your integration's health.
Missing Shipment Orders
This module lists shipment orders that have failed to download from your sales channels into Logiwa IO. Currently, this report only displays channel orders from
Shopify. For each failed order, you can see the specific error code that caused the failure. By understanding why an order didn't download, you can quickly take corrective action.
Benefit: This report provides immediate visibility into orders that failed to enter the fulfillment process. Instead of discovering a missing order, you can proactively identify the issue using the specific error code, fix the root cause (like a product data error in Shopify), and re-process the order to prevent delays and customer dissatisfaction.
Troubleshooting: Clicking on the error code link will redirect you to a detailed troubleshooting guide for that specific error, helping you resolve the issue efficiently.
Following Error Codes are ignored and not reflected to the Missing Shipment Orders:
FulfillmentOrders not found in the specified location
Order lines are already fulfilled on Channel
If an order listed in the Missing Shipment Orders is successfully downloaded when the Download Orders service is rerun, the Shipment Order will be removed from the Missing Shipment Orders list.
Time Frame: This list displays orders from the last two weeks. Orders older than this are automatically removed from the list.
Field | Description |
Order Code | The Shipment Order Code in Logiwa |
Channel Order Number | The order number as it appears in the sales channel |
Channel Setup Name | The name of your store connection setup in Logiwa IO |
Channel | The sales channel the order originated from |
Client | The client associated with the shipment order |
Last Error Code | The specific error message explaining why the order failed to download |
Order Date | The date the order was created in the sales channel |
Update Date | The date the order was last updated in the sales channel. |
Recent Errors
The Recent Errors module provides a summarized view of the errors encountered during the order download process from your sales channels. Like the Missing Shipment Orders report, this currently focuses on orders from Shopify. This report groups errors by type, showing you the total number of occurrences and how many orders were affected by each error. This helps you identify recurring problems that may be impacting a large number of orders.
Benefit: By consolidating errors, this report helps you distinguish between isolated incidents and systemic problems. Seeing that a single error type has affected numerous orders allows you to prioritize fixing the underlying cause, saving time and preventing future order failures on a larger scale.
Troubleshooting: You can click the error reason link to access the relevant troubleshooting article for a quick resolution.
Following Error Codes are ignored and not reflected to the Recent Orders:
FulfillmentOrders not found in the specified location
Order lines are already fulfilled on Channel
Time Frame: This list displays errors from the last two weeks. Entries older than this are automatically removed.
An order that is listed in the Missing Shipment Orders and included in the Recent Orders calculations will continue to be part of those calculations within the two-week time frame, even if it is later removed from the Missing Shipment Orders list after receiving a Success from the Download Order service.
Field | Description |
Error Reason | The specific error message explaining why the order failed to download |
Channel Setup Name | The name of your store connection setup in Logiwa IO |
Channel | The sales channel the order originated from |
Client | The client associated with the shipment order |
Num. of Occurrence | The total number of times this specific error has occurred |
Num. of Affected Order | The total number of unique orders affected by this error. |
Last Occurrence Date | The date and time the most recent error of this type was logged. |
Workflow Blocked Shipment Orders
This module displays shipment orders that have been blocked due to a workflow rule, whether it was fully or partially affected. The report includes all affected shipment orders, not just those originating from a sales channel.
Benefit: This report provides crucial visibility into your automated processes. Its primary benefits include:
Workflow Transparency: Instead of orders simply not appearing, this report shows you precisely which workflow and which specific action prevented an order from being processed. This eliminates guesswork when troubleshooting your automation rules.
Proactive Error Resolution: By seeing which orders are blocked, you can proactively investigate the cause. Whether an order was blocked intentionally by a rule or accidentally due to a misconfiguration, you have the information needed to resolve the issue before it impacts fulfillment.
Detailed Impact Analysis: The "Fully or Partially" status tells you the exact impact of a workflow. A "Fully" blocked order was stopped entirely, while a "Partially" blocked order may have had a specific SKU removed but could still be processed, allowing you to prioritize your actions accordingly.
Workflow Auditing: The report serves as a log to confirm that your workflows are functioning as intended. You can verify that rules designed to stop certain types of orders are catching the correct ones, ensuring your automation is both effective and accurate.
Important Notes:
If a listed order is not a Store Order, the Channel and Channel Setup Name fields will be blank.
If a Delete SKU action is applied to a single-line order, the order will not be created in Logiwa. However, it will appear in this report with a
Partially status because the workflow action was processed.
Time Frame: This list displays orders from the last two weeks, and older entries are removed from this list.
Field | Description |
Order Code | The Shipment Order Code in Logiwa |
Channel Setup Name | The name of your store connection setup in Logiwa IO |
Channel | The sales channel the order originated from |
Client | The client associated with the shipment order |
Order Date | The date the order was created in the sales channel |
Fully or Partially | Indicates if the entire order was blocked Fully or if only specific lines were affected Partially |
Workflow Name | The name of the workflow that affected the order. A hyperlink redirects to the workflow setup |
Action Name | The specific action within the workflow that caused the block |
Warehouse | The warehouse associated with the shipment order |
Product Listing Exceptions
This module is designed to help you identify and manage discrepancies in your product listings across all integrated sales channels. It highlights two main types of issues:
SKU Difference: This occurs when a Logiwa SKU does not match the Seller SKU on the sales channel.
Multi Listing: This flag appears when a single Logiwa Product is linked to multiple Store Products in a Channel Setup.
You can use this report to verify whether these exceptions are intentional or require correction.
Benefit: This screen enables proactive data hygiene for your product catalog. By flagging potential mismatches and duplicate links between Logiwa and your sales channels, it helps you prevent inventory sync errors, incorrect fulfillment, and overselling before they happen.
Listing Updates: If you make changes in Product Listings > Linked Products by unlinking or modifying a listing, the corresponding entry in the Product Listing Exceptions report will be updated or removed.
New Exceptions: Similarly, if a newly added product listing creates a SKU Difference or Multi Listing scenario, it will automatically appear in this report for your review.
Field | Description |
Logiwa SKU | The SKU of the product as it is defined in Logiwa IO |
Seller SKU | The SKU of the product as it is listed on the sales channel |
Channel Setup Name | The name of your store connection setup in Logiwa IO |
Channel | The sales channel the order originated from |
Client | The client associated with the shipment order |
Issue Type | The category of the exception, either SKU Difference or Multi Listing. |
Listing Date | The date the product listing was created or last updated. |