How to set up a Snapfulfill Fulfillment Channel [Step-by-step guide]

Modified on Wed, 22 May at 12:03 AM

To connect Snapfulfill, you will have to, first, create a Fulfillment Channel connection, and then, set up the connection parameters.

Once the connection has been established between the system and techOMS, you will be able to push Sales Orders, pull inventory levels and shipments, send and get receipts, get stock updates and synchronize inventory.


The process consists in two phases:

1) Create the channel

2) Configure additional parameters


NOTE: Make sure that you are operating at the right Vendor/Warehouse beforehand.



CREATE CHANNEL


To create a Fulfillment Channel you will have to follow the instructions in How to set up Warehouses and Fulfillment Channels for an Account [Step-by-step guide]


Once you have added it, proceed to the following section.


CONFIGURE ADDITIONAL PARAMETERS 


To configure additional parameters:


1) Click on the created channel's name in the list



2) Add/Change/Set parameters according to each section as required (click to enhance):



SECTIONS


A) QUICK ACTIONS, allows to perform additional/quick actions:

  • SaveSaves and commits changes
  • Delete: Deletes the channel connection


B) VIEW SELECTION, allows to change the different view modes:

  • Main Settings (default): Allows to review and set the basic connection settings
    • Application: Connection type
    • Connection name: Display name for the connection, can be edited if required for more convenient identification if there are many
    • Sync Actions: Displays information about the synchronization actions and last activity, as well as allowing manual logging 
  • Advanced Settings
    • PII configuration: Allows to configure the PII behavior
    • Reference templates: Allows to configure Reference Number Templates
    • UOM: As detailed in Units of Measurement
    • API Validation Rules: Allows to define rules based on entity, field and status
    • Backorder Mode and Allow Backorder Partial:
      • Manage in TechOMS and Allow Partial uncheckedtechOMS will check stock availability and

        if the goods are enough, it will send the full shipment to the WMS; if the goods are NOT enough, it will NOT send any shipment(s) to WMS

      • Manage in TechOMS and Allow Partial checked: techOMS will check stock availability and if the goods are enough, it will send the full shipment to the WMS; if the goods are NOT enough, then techOMS it will send the PARTIAL shipment to the WMS
      • Manage in Fulfillment Channel: techOMS will NOT check stock availability and will always send the FULL shipment to the WMS
    • Inventory Status to Include: Allows to define the values to include for Inventory Status (write value, enter to confirm)
    • Extension Digit and GS1 Company Prefix: Determines this value for label generation
  • Carrier Mappings: Allows to review and set Carrier name mappings between the WMS connection and techOMS as detailed here: How to map Carriers in a Fulfillment Channel [Step-by-step guide]
  • SKU Mappings: Allows to review and set SKU mappings between the WMS connection and techOMS as detailed here: How to map SKUs in a Fulfillment Channel [Step-by-step guide]
  • Reference Mappings: If available, set or modify reference mappings between techOMS and the Fulfillment channel; each field targets a reference (Shipment and Receipt reference and PO) for which you can select which variable you will use for each case

  • Integrations: Allows to configure connections to the external systems interacting with the channel (WMS, techSHIP)



NOTE: If you wish to set up automations for the channel, follow the steps here: How to configure Recurring Jobs for Sales/Fulfillment channel Automation [Step-by-step guide]



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article