How to set up an OSA Fulfillment Channel [Step-by-step guide]

To connect OSA, first create a Fulfillment Channel connection, and then set up the connection parameters.

Once the connection is established between the system and techOMS, you can push Sales Orders, pull inventory levels and shipments, send and get receipts, get stock updates, and synchronize inventory.

This is a two-phase procedure:

1. Create the Fulfillment Channel
2. Configure additional parameters

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

CREATE THE FULFILLMENT CHANNEL

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

Once added, proceed to the following section.

CONFIGURE ADDITIONAL PARAMETERS 

To configure additional parameters:

1. Click Channels from the left menu under the Fulfillment Channels section. 

2. Click on the created channel's name in the list.

3. Modify parameters in each section as needed. Press Save to apply your changes.

SECTIONS

A) VIEW SELECTION allows changing the different view modes:

• Main Settings (default): Allows reviewing and setting the basic connection settings.
• Advanced Settings: Allows defining backorder behavior, PII, reference templates, Units of Measurement, and API Validation Rules. For backorder, you will have:
  • Backorder Mode and Allow Backorder Partial:
    • Manage in TechOMS and Allow Partial unchecked: techOMS checks stock availability. If enough goods are available, it sends the full shipment to the WMS. If not, it does not send any shipment to the WMS.
    • Manage in TechOMS and Allow Partial checked: techOMS checks stock availability. If enough goods are available, it sends the full shipment to the WMS. If not, it sends the partial shipment to the WMS.
    • Manage in Fulfillment Channel: techOMS does NOT check stock availability and always sends the full shipment to the WMS.
• Carrier Mappings: Allows reviewing and setting 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 reviewing and setting 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: Allows reviewing and setting reference mappings between techOMS and OSA. Fields are mapped only from techOMS to OSA. Refer to How to map References in a Fulfillment Channel [Step-by-step guide] for more details.
  

• Integrations: Allows configuring connections to the external systems interacting with the channel (WMS, techSHIP, etc.):
  • Domain: Domain obtained from the warehouse URL (e.g., XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX).
  • API Token: API Token used to connect to OSA. You can get this token by setting up an api-key and secret in OSA, and encoding both in base 64 using the format api-key:secret.
  • Vendor External Id: Vendor identifier within OSA. It links a specific supplier between techOMS and OSA. Contact your OSA representative to get its value.
  • Channel External Id: Channel ID within OSA. It helps associate orders with the correct source. Contact your OSA representative to get its value.
    
    

B) GENERAL displays and/or allows editing the connection name.

• Key (locked): API key for the channel.
• Application (locked): Connection type.
• Host: techOMS' OSA Fulfillment Channel plugin URL.
• Name: Connection name. You can edit it for more convenient identification within techOMS.
• API Url: OSA API URL to connect to.

C) SYNC ACTIONS displays information about the synchronization actions and last activity, as well as allowing manual logging.

D) QUICK ACTIONS allows to perform additional/quick actions:

• Health Check: Verifies if the connection is active or not.
• Save: Saves and commits changes.
  
• Delete: Deletes the channel connection.

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]