Creating 3PL Order Filters in NetSuite Connector

Create custom filters for 3PL orders in NetSuite Connector to control order imports and logistics provider synchronization.

·2 min read·View Oracle Docs

Creating a filter in NetSuite Connector allows you to manage which orders are imported and sent to third-party logistics (3PL) providers, enabling greater control over your fulfillment processes. This guide will walk you through the necessary steps to create effective filters in your NetSuite Connector setup.

What Are 3PL Filters?

NetSuite Connector utilizes two types of filters that serve to refine the data transferred from NetSuite to your logistics partners:

  • Global Filters: These filters govern what orders are imported into the system and subsequently sent to the logistics provider, applicable across all accounts connected through ShipStation and Amazon MCF.
  • Account Specific Filters: This filter is exclusively available for accounts with multiple 3PL connectors. It allows for more granular control, enabling users to apply restrictions specific to certain providers while using global filters to limit order sync broadly.

How to Create a Filter

Follow these steps to set up a filter in NetSuite Connector:

  1. Log into app.farapp.com.
  2. Choose the appropriate third-party logistics provider from the navigation menu.
  3. Select an account relevant to your 3PL.
  4. Navigate to Settings > Orders.
  5. Expand the Advanced Options section.
  6. Click Edit Order Filters (Global).
  7. Confirm your selection by clicking Ok.
  8. In the Edit 3PL Order Filters (Beta) window, make necessary adjustments:
    • Select Add Filter Row.
    • Choose a field in the Filter Field column. To include a custom field:
      • Select Custom Field and input the field name in the Custom Field field.
  9. In the Filter Operation column, choose the operation you wish to use:
    • Is In List
    • Is Not In List
    • Equals
    • Does Not Equal
    • Is Empty
    • Is Not Empty
    • Contains
    • Does Not Contain
    • Starts With
  10. In the Filter Value column, enter the corresponding value to validate against the chosen operation.
  11. Click Save Changes to apply the edits.
  12. Click Close to finish editing.
  13. Finally, click Save to save all changes.

Important Note

When multiple filters are active, all conditions must be satisfied for orders to pass through the filter process. If any filter condition fails, the order or pick ticket will not be forwarded or synced to the logistics provider.

Key Takeaways

  • Utilize Global and Account Specific filters to control 3PL order syncing.
  • Follow the outlined steps for effective filter creation in NetSuite Connector.
  • Ensure all filter conditions are met to successfully sync orders.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

Is it possible to create 3PL order filters for specific providers within NetSuite Connector?
Yes, using Account Specific Filters, you can create order filters tailored to specific providers when you have multiple 3PL connectors. This allows for granular control over order processing per provider.
What happens if one of the filter conditions fails to be satisfied in 3PL filtering?
If any of the filter conditions fail, the order or pick ticket will not be forwarded or synced to the logistics provider, meaning it won't be processed further in the 3PL system.
Can I use custom fields when creating 3PL order filters in NetSuite Connector?
Yes, you can include custom fields in your filters by selecting 'Custom Field' in the Filter Field column and inputting the required field name.
Do the 3PL filters apply to all accounts connected to NetSuite Connector?
Global Filters apply across all accounts connected via ShipStation and Amazon MCF. Account Specific Filters, however, allow for more targeted filtering for accounts with multiple 3PL connectors.
Source: Creating a Filter Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Integration

View all Integration articles →