Company Settings: SKU Mapping
Settings: SKU Mapping
SKU mapping allows users to set up rules which map incomming SKU's recieved from Sales Channels on orders to specific products and SKU's in Catalog. Sales Channels may be sending in orders with SKU's that differ to those inside the platform so this function allows you to match these up so orders can proceed through automated workflows.
In basic terms, this is just a map that can convert SKUs into different SKUs, Product IDs and Variant details.
Under normal circumstances SKU Maps should be set against dropship company types as they are sepecific to one Sales Channels connection to a single Fulfiller.
This works by accessing the "+ Add SKU Mapping" button which will bring up the options "From SKU", "To Product ID", "To Product SKU", "To Variant ID", "To Variant SKU" and "To Variant Ref". A breakdown of each option can be found below.
- From SKU - Usually the fulfiller SKU, this must be the SKU of which companies do not want to receive.
- To Product ID - Users can specifically target a product ID, this is particularly useful if the product being targeted has the same SKU as other products available.
- To Product SKU - This is the SKU of which users wish to receive from their orders, this is a prominent element of the SKU Map.
- To Variant ID - Users, much like the product ID can also target specific Variant IDs, which is useful when dealing with products with multiple variant options linked.
- To Variant SKU - Users can alternatively target a Variant SKU as opposed to a Variant ID.
- To Variant Ref - Users can alternatively target a Variant Ref as part of a SKU map.
As a bare minimum users should always set a "From SKU" to a "To Product SKU", this will convert the original SKU to what the company wants to receive.
Once users are happy with the SKU mapping set they can simply press the "Save" button and now for any orders of a particular item, the SKU will come in and convert to what is set within the SKU map.
An example of this could be product SKU "Test-SKU" converting to "SKU_Test123"
Still Need Help?
You can access our extensive knowledge base or raise a ticket with our technical support teams using the buttons below
Related Articles
Company Settings: Incoming Orders - SKU Mapping
Company SettingsL Incoming Orders - SKU Mapping There are options to set within the Kornit X platform to influence any incoming SKU Mapping orders and the options have been detailed here. Include Variants In SKU Search - This option will allow users ...Company Settings: Incoming Orders
Company Settings: Incoming Orders This details the settings that can be enabled or disabled for all incoming orders to the Kornit X System, these include the following. Allow Colour / Size Population from Variant - With this toggle enabled for any ...Company Settings: Razer GRN
What is Razer GRN in relation to Company Settings? The Razer GRN settings relate to the Accounting Integration Kornit X has built to connect to the Razer accounting systems. PO Item Counts: This is a list of SKUs by PO Number with a count of how many ...Settings: Companies
What are Companies? This section of the Platform is for the management and creation of Companies within the entire system. There are multiple types of Company types supported and a breakdown of each type can be found here. What are Companies? ...Company Settings: Order API (v2.2)
Company Settings: Order API V2.2 Kornit X has some advanced settings that can be enabled for those using the Order API V2.2 and these options have been built to improve efficiency and users of the Order API v2.2. Please note, this option will only ...