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

To connect Logiwa, first create the Fulfillment Channel connection, and then set up its parameters. This Fulfillment Channel connects techOMS with the Logiwa IO Fulfillment Platform.

Once the connection is established between the channel and techOMS, you can use its supported features as listed in: techOMS Fulfillment Channels - Master List [Guides List].

This article is divided into the following sections:

1. Onboarding Requirements
2. Create the Fulfillment Channel
3. Configure Additional Parameters

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

  NOTE :

I. ONBOARDING REQUIREMENTS

• Logiwa API access and connection details (API URL).
• Logiwa credentials: Email and Password.
• Logiwa account identifiers required by the integration: Client ID and Default Vendor (for PO's only).

II. CREATE THE FULFILLMENT CHANNEL

To create a Logiwa Fulfillment Channel, follow: How to Create a Fulfillment Channel [Step-by-step guide].

III. 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.
3. Use the highlighted areas in the screenshot below and configure the required settings.

SECTIONS

A) QUICK ACTIONS lets you perform additional actions:

• Sync: Enables manual synchronization as detailed in How to Synchronize data through a Fulfillment Channel [Step-by-step guide].
  
  Sync options(availability varies by channel, user permissions, and channel configuration):
  • Export Products To Channel
  • Receive Inventory Levels From Channel
  • Receive Shipments From Channel
  • Receive Receipts From Channel

 WARNING: Cancel Receipt is not supported for this channel.

 NOTE: Only Tags that already exist in Logiwa are mapped when orders are exported from techOMS. Tags are mapped by ID, so tags that do not exist in Logiwa are ignored and will not be visible on the Logiwa side.

  NOTE :

• Save: Saves and commits changes.
• Delete: Deletes the channel connection.

B) VIEW SELECTION allows you to navigate the different tabs:

• Main settings (default): Configures general and automation behavior using: Main Settings of a Beta Fulfillment Channel [Information].
• Advanced settings: Configures additional system/privacy settings using: How to manage Fulfillment Channels Advanced settings [Step-by-Step guide].
• Channel settings:
  • Api Url: Logiwa API endpoint (base URL) used by the connector.
      NOTE :
      WARNING :
  • Email: Email (username) used to authenticate with Logiwa.
      NOTE :
      WARNING :
  • Password: Password used to authenticate with Logiwa.
  • ClientId: Logiwa client identifier required for the API connection.
  • Default Vendor (for PO's only): Default vendor name used by Logiwa when creating purchase orders through this channel.
     NOTE: This setting only works when creating purchase orders. If you need a different vendor per purchase order, you can override the vendor using Reference Mappings.
  • Inventory Status: Inventory status used during inventory synchronization.
  • Shipment Order Type: Shipment type name used for shipment processing/sync.
  • Purchase Order Type: Receipt type name used for receipt processing/sync.
  • Throughput: Default throughput configuration for the channel.
• Carrier Mappings: If available for this channel, sets carrier/service name mappings as detailed in How to map Carriers and Services in a Fulfillment Channel [Step-by-step guide].
• SKU Mappings: If available for this channel, reviews and sets SKU mappings as detailed in How to map SKUs in a Fulfillment Channel [Step-by-step guide].
• Reference Mappings: If available for this channel, reviews and sets reference mappings.

NOTE: Follow How to configure Automations for Sales/Fulfillment channels [Step-by-step guide] to configure Recurring Jobs or Webhooks when these modes are available for the channel.

• Webhooks: If this channel supports webhooks and exposes the Webhooks tab, allows configuring webhook-based automations.