Commerce7 and ShipCompliant remain essential to both order flows for compliance checks and state reporting. The primary difference is how shipping orders reach ACP for fulfillment.

With the traditional ShipCompliant flow, ShipCompliant sits in the middle of the shipping-order import process. With the Wineshipping app flow, the app imports eligible Commerce7 orders directly into ACP while ShipCompliant continues to support compliance and reporting in parallel.


Option One: ShipCompliant Is the Order-Import Path

In this flow, Commerce7 sends orders to ShipCompliant for compliance checks and state reporting. ShipCompliant then becomes the source used to create the shipping order in ACP.

Once Wineshipping processes, packs, and labels the order, tracking is sent to ShipCompliant for reporting. Commerce7 can then retrieve the tracking information from ShipCompliant to fulfill the order.

Considerations with the ShipCompliant import flow
  • Club orders must be batched through ShipCompliant before they can enter ACP. If batching is delayed, those orders may remain in ShipCompliant instead of moving to the warehouse.

  • Commerce7 only checks ShipCompliant for tracking every 4 hours on orders created within the prior 90 days. An order held for weather beyond that window may require manual intervention to ensure Commerce7 is fulfilled.

  • Commerce7 order tags do not pass into ACP through the ShipCompliant import.

  • Bundle orders import with component SKUs only; the parent bundle SKU is not available in ACP.

  • Refunds and exchanges require manual coordination in Commerce7 and ShipCompliant to ensure ACP is updated correctly and to prevent duplicate shipments.


Option Two: Wineshipping App Imports Orders Directly from Commerce7

With the Wineshipping app, Commerce7 still sends orders to ShipCompliant for compliance and state reporting. The Wineshipping app then imports eligible shipping orders directly from Commerce7 into ACP on the schedule and timeframe configured in the Batch Order settings.

This removes ShipCompliant as the gate for shipping-order creation while retaining the compliance and reporting processes the winery relies on.

Once Wineshipping fulfills the order, the app posts tracking directly back to Commerce7 and also sends the tracking event to ShipCompliant for reporting.

Compliance Protection Remains in Place

Transitioning order import to the Wineshipping app does not bypass compliance.

When the Compliance Check setting is enabled, the app reviews the Commerce7 compliance status before sending an order to ACP. Only orders with an approved status can proceed:

  • Compliant

  • Forced / Forced Compliance

  • No Compliance Required

Orders in any other compliance status, including Quarantined, are not sent to ACP for fulfillment. This ensures the warehouse is not asked to ship an order that has not cleared the required compliance review.

If an order is later cleared in Commerce7, the Wineshipping app can process it during a subsequent batch cycle once it has an eligible status.


Benefits of Transitioning to the Wineshipping App

  • Automatic order import across channels

    • The app imports eligible shipping orders across Commerce7 channels during the timeframe set in Batch Order settings. This includes Club orders, so they can flow into ACP automatically without waiting for someone to batch them in ShipCompliant.

  • More dependable tracking for weather-held orders

    • The Wineshipping app posts tracking directly to Commerce7 and does not depend on Commerce7’s 90-day ShipCompliant tracking lookup. This helps prevent older weather-held orders from being left unfulfilled in Commerce7 after they eventually ship.

  • Commerce7 tags are available in ACP

    • Order tags flow into ACP with the order, allowing the winery to use tags for ACP order rules, holds, carrier mappings, routing, order types, and other automation.

  • Parent bundle SKUs can be supported

    • When the Parent Bundle SKU setting is enabled, the Wineshipping app can pass the parent bundle SKU into ACP rather than importing only the bundle components. This gives the winery more flexibility in how bundle orders are represented and processed.

  • Eligible refunds and exchanges can update the original ACP order

    • With Retransmit a Changed Order enabled, the app can process selected refund and exchange events against the original ACP order, provided the order is still eligible to change and has not progressed into warehouse packing. This reduces manual steps and helps prevent duplicate shipments.

  • Inventory and reporting stay connected

    • The Wineshipping app continues to support tracking reporting to ShipCompliant and can sync available-for-sale inventory back to the relevant Commerce7 shipping location.


Summary

The ShipCompliant import flow remains a workable option for wineries that want ShipCompliant to be the source of the shipping order and are prepared to manage batching and manual exceptions.

The Wineshipping app flow is the stronger option for wineries that want a more automated order process. It preserves the Commerce7 data needed for ACP automation, reduces manual Club-order batching, improves tracking reliability for aged weather holds, supports eligible order changes, and still protects against shipping quarantined or otherwise non-compliant orders.