Articles in this section

Configure the GraphQL fulfillment flow

Saikumar Rachamalla
Updated

A new GraphQL-based fulfillment flow, NetSuite fulfillment to Shopify fulfillment (add), is now available under Flows > Fulfillment. This enhanced flow leverages the GraphQL API, unlike the previous flow that uses REST, providing robust support for complex fulfillment scenarios.
Config_1.png

Key benefits 

  • GraphQL integration: Utilizes Shopify’s GraphQL API, enabling more flexible data handling.

  • Supports complex scenarios:

    • Split carts

    • Subscriptions

    • Multi-location and partial fulfillments

Deprecation of the REST-based Flow

The existing REST-based flow [Deprecated] NetSuite fulfillment to Shopify fulfillment (add) will continue to operate since Shopify has not set a deprecation timeline; however, Celigo will discontinue support for the [Deprecated] NetSuite fulfillment to Shopify fulfillment (add) flow after October 31, 2025.

  • Flows > Fulfillment 

    • [Deprecated] NetSuite fulfillment to Shopify fulfillment (add)

Config_2.png

Notes

    • The existing REST-based flow [Deprecated ](NetSuite fulfillment to Shopify fulfillment (add)) will not be removed immediately.
    • The deprecated flow will not receive any new enhancements.
    • All future enhancements will be delivered exclusively through the new GraphQL flow.
    • To clearly distinguish between the REST and GraphQL flows, the REST-based flow is now labeled with a “[Deprecated]” prefix.
    • The Enable GraphQL fulfillment import setting is now removed from Settings > Fulfillment.
    • New installations will not include the old flow and will display only the GraphQL-based flow.

To take full advantage of Shopify’s latest and upcoming features, we recommend migrating to the new GraphQL flow.

Migrate to the new fulfillment flow

  1. Open your Shopify - NetSuite integration app.

  2. Navigate to Flows > Fulfillment. 

  3. Turn on the toggle for the flow: NetSuite fulfillment to Shopify fulfillment (add).

    Note

    If you want to test the new flow without disabling the old one, ensure that the REST-based flow is not scheduled to run at the same time as the GraphQL flow, or configure filters in the REST flow to exclude any data that the GraphQL flow will process.

  4. Review the following:
    1. Existing configurations
    2. Custom mappings (reapply them as needed). To review, navigate to the NetSuite Fulfillment to Shopify Fulfillment (Add) flow, select Post Order Fulfillment to Shopify Import, and click Mappings.
      Notes: 
      • Standard mappings are automatically migrated to the new GraphQL flow.
      • If you have previously enabled the Enable GraphQL fulfillment import checkbox, your custom mappings have already been migrated. 
       
      Config_5.png
  5. Go to Settings > Fulfillment.
  6. Perform one of the following:
    1. From the NetSuite Saved Search to sync item fulfillments dropdown, select your desired 'saved search’. Click Refresh to fetch the latest records from NetSuite. [OR]
      Config_3.png

    2. Open the NetSuite fulfillment to Shopify fulfillment (add) flow, click Get order fulfillment from NetSuite export, and update the saved search ID.
      Config_4.png

  7. Click Save to apply the changes.
  8. Return to Flows > Fulfillment and run the GraphQL flow: NetSuite fulfillment to Shopify fulfillment (add).

Once the GraphQL flow runs successfully and you are satisfied with the data synced, you may proceed with disabling the REST-based flow prefixed as Deprecated.

Additional considerations

  • Scheduling: Make sure to schedule the GraphQL flow manually based on your business requirements.

  • Disabling the old flow: After you’ve tested and confirmed that the new flow works as expected, you can disable the old flow labeled as Deprecated, since it’s no longer required.

Limitation: The flow supports up to 250 fulfillment orders per Shopify order. However, it does not support scenarios where a single line item is included in multiple fulfillment orders, as this typically results from manual splitting and is not considered a valid business use case.