Welcome to the JM Wholesale Integration Guide for Flxpoint! This guide walks you through connecting, configuring, and managing your integration to streamline inventory and fulfillment.
How to Connet
Step 1: Log into your Flxpoint account and go to the Sources tab.
Step 2: Click + Add Source (or Configure Single Source) to create a new JM Wholesale source.
Step 3: Enter basic source details (e.g., vendor name "JM Wholesale") and click Save or Next.
Step 4: Under Account Settings → General → Company Information, fill in your Company Name, Logo, Website, Phone, Email & Address.
Step 5: Follow the Source Wizard prompts: Vendor Setup, Assign Vendor, Order Fulfillment, Shipping Options, Source Location, then click Done.
Step 6: Under Integrations, choose processes (GIS, GIP, Send Fulfillment Requests, Get Shipments) and click Start Creating Integrations.
Step 7: Configure connection details:
No credentials required: Flxpoint uses your Company Information.
Connection Name: Name it (e.g., “JM Wholesale – GIS”).
Test Connection: Verify your feed.
Step 8: When tests pass, click Save Connection.
Step 9: On Configure Settings, adjust advanced options and click Save and Proceed.
Step 10: Select or create a Mapping Template, map fields, then click Save and Complete.
Step 11: Your JM Wholesale integration is now active—Flxpoint will sync automatically.
×
![]()
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates
Get Inventory (Primary)
Supported | JM Wholesale - Get Inventory [Primary]
Introduction to JM Wholesale Get Inventory [Primary] Integration
Welcome to the JM Wholesale Get Inventory [Primary] integration guide! This section will help you connect to JM Wholesale, retrieve their product inventory data, and integrate it into your system. Whether you’re new to inventory management or an experienced user, we’ll guide you through each step—from connecting the integration to mapping product data—so you can manage your inventory effortlessly. Let’s get started!
Purpose of This Integration
The JM Wholesale Get Inventory [Primary] integration allows you to fetch and manage product inventory data directly from JM Wholesale, ensuring your system reflects the latest product details and stock levels. This integration:
- Retrieves key product information like SKUs, quantities, and other details from JM Wholesale.
- Processes the data to match your system’s inventory structure for consistency and accuracy.
- Helps maintain accurate stock levels by archiving or un-archiving inventory as needed.
This integration streamlines inventory management, keeping your product listings up to date and your operations running smoothly. How the Integration Works
The JM Wholesale Get Inventory [Primary] integration follows a clear process to bring inventory data into your system:
1. Connecting to JM Wholesale: Establishes a connection with JM Wholesale’s data source. No additional connection information is required for this integration.
2. Configuring Settings: Lets you customize how inventory is handled, such as whether to archive unavailable products.
3. Mapping Data: Uses a mapping template to align JM Wholesale’s product data with your system’s inventory fields (e.g., mapping their SKU to your Parent SKU).
4. Running the Integration: Fetches and processes the data, either manually or on a schedule, to update your inventory.
Note: Since JM Wholesale doesn’t require additional connection details, setup is quick and straightforward. The key step is mapping the data to your system, which we’ll cover in detail below. Configuration Options
You can customize the integration with these settings to suit your needs:
- Archive/Un-Archive Inventory: Decide whether to archive inventory not found in JM Wholesale’s feed (default: No). Archiving sets the quantity to zero, while un-archiving reactivates it with the mapped quantity. Enable this only if JM Wholesale is your primary inventory source; otherwise, keep it disabled if you use Get Inventory [Secondary] for this source.
- Scheduling: Choose to run the integration manually or schedule it to run automatically (e.g., daily at 6 AM UTC).
Setup Instructions
Follow these steps to set up the JM Wholesale Get Inventory [Primary] integration:
1. Connect the Integration: In your system, navigate to the "Get Inventory [Primary]" section under "Integrations." Select "JM Wholesale" from the list. You’ll see a message: “No additional connection information is needed for this integration.” Click “Save and Proceed” to continue.
2. Configure Settings: Adjust the following options:
- Archive/Un-Archive Inventory: Toggle this setting based on your needs. We recommend setting it to “No” if JM Wholesale isn’t your primary inventory source or if you’re using Get Inventory [Secondary] for this supplier.
- Scheduling: Optionally, enable automatic scheduling (e.g., daily at 6 AM UTC) to keep your inventory updated without manual intervention.
Once configured, click “Save and Proceed.” 3. Define a Mapping Template: Create a mapping template to match JM Wholesale’s data to your system’s fields. This ensures the inventory data is imported correctly. We’ll cover this in detail below.
4. Run the Integration: After setting up the mapping template, run the integration manually by clicking “Run Integration” or let it run on your scheduled time.
Mapping Template Overview
A mapping template ensures JM Wholesale’s inventory data aligns with your system’s fields. It defines how their product data (e.g., SKU, quantity) maps to your inventory fields (e.g., Parent SKU, Quantity). Let’s break down what’s covered, how to use it, and provide specific mapping suggestions to get you started.
Interface Overview
- The mapping screen is labeled “JM Wholesale - Get Inventory [Primary]” at the top. You can name your template (e.g., “JM Wholesale - Get Inventory [Primary] 1”).
- There are buttons at the top: Delete (remove the template), Duplicate (create a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Shows options for handling JM Wholesale’s data (e.g., “Field,” “Value,” “Don’t Map”).
- Right Column (To Inventory Parent Field): Lists your system’s fields (e.g., “Parent SKU,” “Quantity”).
What’s Covered in the Mapping Template The mapping template allows you to map JM Wholesale’s data to two main categories in your system:
- Inventory Parent Fields: These are the main product details, such as:
- Parent SKU (required): The unique identifier for the product.
- Title, Description, Brand, Categories (1, 2, 3): Core product information.
- All Attributes, All Custom Fields, All Images, All Options: Bulk mapping for additional product details.
- Custom Fields (100 available): Additional fields for specific product attributes.
- Inventory Variant Fields: These are details for product variants, such as:
- Master SKU, SKU (required): Identifiers for the variant.
- Quantity, Cost, MSRP, MAP: Pricing and stock information.
- GTIN, UPC, MPN, ASIN: Product identifiers.
- Weight, Height, Length, Width, Dimension Unit: Physical attributes.
- Allow Backorders, Archived, Bin Location: Inventory management settings.
- Dropship Fee, Shipping Cost, Source List Price: Additional costs.
- Custom Fields (100 available), Custom Aggregate Fields (10 available): Extra fields for variant-specific data.
What Can Be Used (Mapping Options) For each field, you can choose how to handle JM Wholesale’s data with these options:
- Don’t Map: Skip the field entirely. It won’t be imported (e.g., ignoring “Description” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Weight” to empty).
- Field / Direct Copy: Copy the data directly from JM Wholesale’s feed (e.g., copying their SKU to your Parent SKU).
- Value: Set a specific value for the field (e.g., setting “Weight Unit” to “pound” for all products).
- Mapping Set: Apply a transformation to the data (e.g., converting categories to a specific format).
- Rules: Use conditional logic to process the data (e.g., “If Quantity < 5, set to 0”). This is optional and can be skipped if you’re new to mapping.
Required Fields Some fields are mandatory and must be mapped to ensure the integration works correctly:
- Parent SKU: Must be mapped to JM Wholesale’s SKU field to uniquely identify each product.
- Master SKU and SKU (Variants): Required to identify product variants.
If these fields aren’t mapped, the integration may fail to process the data. Specific Mapping Suggestions Here are suggested mappings for key fields to help you get started with JM Wholesale’s data. Since the exact field names from JM Wholesale’s feed aren’t specified, we’ll assume typical field names (e.g., “SKU,” “Quantity”) and guide you on how to map them to your system. Adjust these based on the actual field names in JM Wholesale’s feed.
Parent SKU: The unique identifier for the product.
- Suggested Mapping: Map to JM Wholesale’s “SKU” field using “Field / Direct Copy.”
- Reason: This ensures each product is uniquely identified in your system. This field is required.
- Example: If JM Wholesale’s SKU is “JM12345,” this will be set as the Parent SKU.
Title: The product name.
- Suggested Mapping: Map to JM Wholesale’s “ProductName” or “Title” field using “Field / Direct Copy.”
- Reason: Provides the product name for your listings. Special characters may need to be cleaned during processing.
- Example: “Organic Cotton T-Shirt” from JM Wholesale becomes the product title.
Quantity (Variants): The available stock quantity.
- Suggested Mapping: Map to JM Wholesale’s “Quantity” or “StockLevel” field using “Field / Direct Copy.”
- Reason: Keeps your stock levels accurate by reflecting JM Wholesale’s current inventory.
- Example: If JM Wholesale reports a quantity of “50,” your system will update to 50 units.
Cost (Variants): The product cost price.
- Suggested Mapping: Map to JM Wholesale’s “CostPrice” or “Price” field using “Field / Direct Copy.”
- Reason: Provides the cost for pricing calculations and profitability tracking.
- Example: A cost of “$10.00” from JM Wholesale will be imported as the product cost.
Weight (Variants): The product weight.
- Suggested Mapping: Map to JM Wholesale’s “Weight” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Useful for calculating shipping costs. If JM Wholesale doesn’t provide this, you can skip it.
- Example: A weight of “1.5” will be imported for shipping calculations.
Weight Unit (Variants): The unit of measure for the weight.
- Suggested Mapping: If JM Wholesale provides a “WeightUnit” field, map it using “Field / Direct Copy.” Otherwise, set to “pound” using “Value.”
- Reason: Standardizes the weight unit for consistency. Note: Map either Weight Unit or Weight Unit (Abbreviated), not both—Weight Unit takes priority.
- Example: Setting to “pound” ensures all weights are in the same unit.
Category 1: The primary product category.
- Suggested Mapping: Map to JM Wholesale’s “Category” or “ProductCategory” field using “Field / Direct Copy,” or set to “Don’t Map” if not applicable.
- Reason: Organizes products into categories for better inventory management.
- Example: A category of “Apparel” from JM Wholesale will categorize the product accordingly.
All Images (Parent and Variants): Product images.
- Suggested Mapping: Map to JM Wholesale’s “ImageURL” or “Images” field using “Field / Direct Copy,” or set to “Don’t Map” if images aren’t needed.
- Reason: Imports product images for your listings. Bulk mapping saves time if JM Wholesale provides multiple images.
- Example: An image URL like “https://jmwholesale.com/images/JM12345.jpg” will be imported.
Allow Backorders (Variants): Whether the product can be backordered.
- Suggested Mapping: Map to JM Wholesale’s “BackorderAllowed” field using “Field / Direct Copy,” or set a specific value (e.g., “No”) using “Value.”
- Reason: Controls whether out-of-stock variants can be added to purchase orders or fulfillment requests.
- Example: Setting to “No” prevents backordering for all variants.
Tips for Mapping
- Start with the required fields (Parent SKU, Master SKU, SKU) to ensure the integration runs smoothly.
- Use “Direct Copy” for fields like Quantity or Cost if JM Wholesale’s data matches your needs.
- For fields like Weight Unit or Dimension Unit, consider using “Value” to set a consistent unit (e.g., “pound” or “inch”) if JM Wholesale doesn’t provide this data.
- If you don’t need certain fields (e.g., ASIN or Dropship Fee), select “Don’t Map” to skip them.
- Review JM Wholesale’s feed to confirm the exact field names (e.g., “ProductName” vs. “Title”) and adjust mappings accordingly.
Conclusion
Congratulations! You’ve successfully set up the JM Wholesale Get Inventory [Primary] integration. With your connection established, settings configured, and mapping template in place, you’re now ready to seamlessly retrieve and manage inventory data from JM Wholesale. Your product listings will stay up to date with accurate stock levels and details, helping you keep your business running smoothly. If you encounter any issues or need further assistance, feel free to reach out to your support team. Happy inventory management!
Get Inventory (Secondary)
Supported | JM Wholesale - Get Inventory [Secondary]
Introduction to JM Wholesale Get Inventory [Secondary] Integration
Welcome to the JM Wholesale Get Inventory [Secondary] integration guide! This section will walk you through the process of connecting to JM Wholesale as a secondary inventory source, retrieving product data, and integrating it into your system. Designed for both beginners and experienced users, this guide covers each step—from establishing the connection to mapping data—so you can efficiently update your inventory. Let’s dive in!
Purpose of This Integration
The JM Wholesale Get Inventory [Secondary] integration enables you to fetch and manage product inventory data from JM Wholesale as a secondary source, complementing your primary inventory data. This ensures your system stays updated with the latest stock levels and pricing from JM Wholesale. This integration:
- Retrieves essential product information like SKUs, quantities, and pricing from JM Wholesale.
- Processes the data to align with your system’s inventory structure, ensuring consistency.
- Updates existing inventory records without creating new products, unless specified.
This integration helps you maintain accurate inventory by supplementing your primary data, streamlining operations, and ensuring your product listings are current. How the Integration Works
The JM Wholesale Get Inventory [Secondary] integration follows a structured process to update your inventory with secondary data:
1. Connecting to JM Wholesale: Establishes a connection with JM Wholesale’s data source. No additional connection information is required for this integration.
2. Configuring Settings: Allows you to customize how inventory is handled, including archiving options and variant creation settings.
3. Mapping Data: Uses a mapping template to align JM Wholesale’s product data with your system’s inventory fields (e.g., mapping their SKU to your SKU).
4. Running the Integration: Fetches and processes the data, either manually or on a schedule, to update your inventory.
Note: As a secondary integration, this process updates existing products rather than creating new ones, unless you enable the “Allow Create Variant” setting. Since JM Wholesale doesn’t require additional connection details, setup is straightforward. Configuration Options
You can tailor the integration with these settings to fit your needs:
- Archive/Un-Archive Inventory: Decide whether to archive inventory not found in JM Wholesale’s feed (default: No). Archiving sets the quantity to zero, while un-archiving reactivates it with the mapped quantity. We recommend keeping this disabled for secondary integrations to avoid overwriting primary inventory data.
- Allow Create Variant: Choose whether to allow the creation of new variants when running this integration (default: No). Enabling this creates new variants if they don’t already exist in your system.
- Scheduling: Opt to run the integration manually or schedule it to run automatically (e.g., daily at 6 AM UTC).
Setup Instructions
Follow these steps to set up the JM Wholesale Get Inventory [Secondary] integration:
1. Connect the Integration: In your system, navigate to the "Get Inventory [Secondary]" section under "Integrations." Select "JM Wholesale" from the list. You’ll see a message: “No additional connection information is needed for this integration.” Click “Save and Proceed” to continue.
2. Configure Settings: Adjust the following options:
- Archive/Un-Archive Inventory: Toggle this setting based on your needs. We recommend setting it to “No” for a secondary integration to preserve your primary inventory data.
- Allow Create Variant: Toggle this setting to “Yes” if you want to create new variants for products that don’t already exist in your system; otherwise, keep it as “No” to only update existing variants.
- Scheduling: Optionally, enable automatic scheduling (e.g., daily at 6 AM UTC) to keep your inventory updated without manual intervention.
Once configured, click “Save and Proceed.” 3. Define a Mapping Template: Create a mapping template to match JM Wholesale’s data to your system’s fields. This ensures the inventory data is imported correctly. We’ll cover this in detail below.
4. Run the Integration: After setting up the mapping template, run the integration manually by clicking “Run Integration” or let it run on your scheduled time.
Mapping Template Overview
A mapping template ensures JM Wholesale’s inventory data aligns with your system’s fields as a secondary source. It defines how their product data (e.g., SKU, quantity) maps to your inventory fields (e.g., SKU, Quantity). Let’s explore what’s covered, how to use it, and provide specific mapping suggestions to help you get started.
Interface Overview
- The mapping screen is labeled “JM Wholesale - Get Inventory [Secondary]” at the top. You can name your template (e.g., “JM Wholesale - Get Inventory [Secondary] 1”).
- There are buttons at the top: Delete (remove the template), Duplicate (create a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Shows options for handling JM Wholesale’s data (e.g., “Field,” “Value,” “Don’t Map”).
- Right Column (To Inventory Variant Field): Lists your system’s fields (e.g., “SKU,” “Quantity”).
What’s Covered in the Mapping Template The mapping template for the secondary integration focuses on updating variant-level data in your system, since it’s designed to complement your primary inventory. It includes:
- Inventory Variant Fields: These are details for product variants, such as:
Note: Unlike the primary integration, this template does not include parent-level fields (e.g., Parent SKU, Title, Description) because the secondary integration updates existing products rather than creating new ones, unless “Allow Create Variant” is enabled. - SKU (required): The unique identifier for the variant.
- Quantity, Cost, MSRP, MAP: Pricing and stock information.
What Can Be Used (Mapping Options) For each field, you can choose how to handle JM Wholesale’s data with these options:
- Don’t Map: Skip the field entirely. It won’t be updated (e.g., ignoring “Cost” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Quantity” to empty).
- Field / Direct Copy: Copy the data directly from JM Wholesale’s feed (e.g., copying their SKU to your SKU).
- Value: Set a specific value for the field (e.g., setting “Quantity” to “0” for all variants).
- Mapping Set: Apply a transformation to the data (e.g., adjusting pricing formats).
- Rules: Use conditional logic to process the data (e.g., “If Quantity < 5, set to 0”). This is optional and can be skipped if you’re new to mapping.
Required Fields The following field is mandatory and must be mapped to ensure the integration works correctly:
- SKU: Must be mapped to JM Wholesale’s SKU field to identify and update the correct variants in your system.
If this field isn’t mapped, the integration may fail to process the data. Specific Mapping Suggestions Here are suggested mappings for key fields to help you get started with JM Wholesale’s secondary data. Since the exact field names from JM Wholesale’s feed aren’t specified, we’ll assume typical field names (e.g., “SKU,” “Quantity”) and guide you on how to map them to your system. Adjust these based on the actual field names in JM Wholesale’s feed.
SKU: The unique identifier for the variant.
- Suggested Mapping: Map to JM Wholesale’s “SKU” field using “Field / Direct Copy.”
- Reason: This ensures the integration can identify and update the correct variants in your system. This field is required.
- Example: If JM Wholesale’s SKU is “JM12345-V1,” this will be matched to the corresponding variant in your system.
Quantity: The available stock quantity.
- Suggested Mapping: Map to JM Wholesale’s “Quantity” or “StockLevel” field using “Field / Direct Copy.”
- Reason: Updates your stock levels to reflect JM Wholesale’s current inventory, ensuring accuracy for secondary data.
- Example: If JM Wholesale reports a quantity of “50,” your system will update the variant’s quantity to 50 units.
Cost: The product cost price.
- Suggested Mapping: Map to JM Wholesale’s “CostPrice” or “Price” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Updates the cost for pricing calculations and profitability tracking, if desired.
- Example: A cost of “$10.00” from JM Wholesale will update the variant’s cost in your system.
MSRP: The manufacturer’s suggested retail price.
- Suggested Mapping: Map to JM Wholesale’s “MSRP” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Updates the suggested retail price for the variant, if applicable.
- Example: An MSRP of “$20.00” from JM Wholesale will update the variant’s MSRP.
MAP: The minimum advertised price.
- Suggested Mapping: Map to JM Wholesale’s “MAP” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Ensures compliance with minimum pricing rules by updating the MAP for the variant.
- Example: A MAP of “$15.00” from JM Wholesale will update the variant’s MAP in your system.
Tips for Mapping
- Start with the required field (SKU) to ensure the integration runs smoothly.
- Use “Direct Copy” for fields like Quantity or Cost if JM Wholesale’s data matches your needs.
- For fields you don’t need to update (e.g., MAP or MSRP), select “Don’t Map” to skip them and preserve your primary data.
- Review JM Wholesale’s feed to confirm the exact field names (e.g., “StockLevel” vs. “Quantity”) and adjust mappings accordingly.
- Since this is a secondary integration, focus on fields that need updating (e.g., Quantity) and avoid overwriting critical primary data unless necessary.
Conclusion
You’ve successfully set up the JM Wholesale Get Inventory [Secondary] integration! With your connection established, settings configured, and mapping template in place, you can now seamlessly update your inventory with secondary data from JM Wholesale. Your stock levels and pricing will stay accurate, complementing your primary inventory and keeping your operations efficient. If you need further assistance, don’t hesitate to contact your support team. Happy inventory management!
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.
Send Fulfillment Requests
Supported | JM Wholesale - Send Fulfillment Requests
Introduction to JM Wholesale Send Fulfillment Requests Integration
Welcome to the JM Wholesale Send Fulfillment Requests integration guide! This section will guide you through the process of connecting to JM Wholesale to send fulfillment requests (purchase orders) efficiently. Whether you’re new to fulfillment integrations or an experienced user, we’ll walk you through each step—from establishing the connection to mapping order data—so you can streamline your order fulfillment process. Let’s get started!
Purpose of This Integration
The JM Wholesale Send Fulfillment Requests integration allows you to send purchase orders to JM Wholesale for fulfillment, ensuring your orders are processed accurately and efficiently. This integration:
- Maps your Shopify order data (e.g., billing and shipping addresses, line items) to JM Wholesale’s required fields.
- Sends fulfillment requests to JM Wholesale, automating the process of ordering products for your customers.
- Provides options to control the timing of order submissions, such as holding orders for review.
This integration simplifies the fulfillment process, helping you manage orders seamlessly while ensuring JM Wholesale receives the correct information to fulfill them. How the Integration Works
The JM Wholesale Send Fulfillment Requests integration follows a structured process to send purchase orders to JM Wholesale:
1. Connecting to JM Wholesale: Establishes a connection with JM Wholesale’s system. No additional connection information is required for this integration.
2. Configuring Settings: Allows you to customize how orders are sent, including options to hold orders for review and specify sending during business hours.
3. Mapping Data: Uses a mapping template to align your Shopify order data (e.g., billing address, line items) with JM Wholesale’s purchase order fields.
4. Running the Integration: Sends the mapped fulfillment requests to JM Wholesale, either manually or on a schedule.
Note: This integration focuses on sending purchase orders, so it’s crucial to map the necessary fields (like addresses and line items) to ensure JM Wholesale can process your requests accurately. Configuration Options
You can customize the integration with these settings to fit your fulfillment workflow:
- Hold for X Hours: Specify a time period (in hours) to hold purchase orders/fulfillment requests before sending them to JM Wholesale (default: 0). This gives you time to review orders but should not exceed the specified limit to avoid delays.
- Send During Business Hours: Choose whether to send orders only during JM Wholesale’s business hours (default: No). Enabling this ensures orders are sent at appropriate times for processing.
- Scheduling: Opt to run the integration manually or schedule it to run automatically (e.g., daily at 6 AM UTC).
Setup Instructions
Follow these steps to set up the JM Wholesale Send Fulfillment Requests integration:
1. Connect the Integration: In your system, navigate to the "Send Fulfillment Requests" section under "Integrations." Select "JM Wholesale" from the list. You’ll see a message: “No additional connection information is needed for this integration.” Click “Save and Proceed” to continue.
2. Configure Settings: Adjust the following options:
- Hold for X Hours: Enter the number of hours to hold orders before sending (e.g., “2” for 2 hours). Keep this low unless you need extra review time, as delays can impact fulfillment.
- Send During Business Hours: Toggle this to “Yes” if you want to send orders only during JM Wholesale’s business hours; otherwise, keep it as “No” for immediate sending.
- Scheduling: Optionally, enable automatic scheduling (e.g., daily at 6 AM UTC) to send fulfillment requests without manual intervention.
Once configured, click “Save and Proceed.” 3. Define a Mapping Template: Create a mapping template to match your Shopify order data to JM Wholesale’s purchase order fields. This ensures the fulfillment requests are formatted correctly. We’ll cover this in detail below.
4. Run the Integration: After setting up the mapping template, run the integration manually by clicking “Run Integration” or let it run on your scheduled time.
Mapping Template Overview
A mapping template ensures your Shopify order data aligns with JM Wholesale’s purchase order requirements. It defines how your order fields (e.g., billing address, line items) map to JM Wholesale’s fields. Let’s break down what’s covered, how to use it, and provide specific mapping suggestions to help you get started.
Interface Overview
- The mapping screen is labeled “JM Wholesale - Send Purchase Orders” at the top. You can name your template (e.g., “JM Wholesale - Send Purchase Orders 1”).
- There are buttons at the top: Delete (remove the template), Duplicate (create a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Shows options for handling your Shopify data (e.g., “Field,” “Value,” “Don’t Map”).
- Right Column (To Shopify Field): Lists JM Wholesale’s fields (e.g., “Address 1,” “SKU”) under categories like Billing Address, Line Item, Order, and Shipping Address.
What’s Covered in the Mapping Template The mapping template organizes your Shopify order data into four categories to match JM Wholesale’s purchase order requirements:
- Shopify Billing Address Fields: Maps billing address details, such as:
- Address 1, Address 2, City, Company, Country, Country Code
- First Name, Last Name, Name, Phone
- Province, Province Code, Zip
- Latitude, Longitude
- Shopify Line Item Fields: Maps individual line item details, such as:
- Price, Quantity, SKU
- Shopify Order Fields: Maps order-level details, such as:
- Note
- Shopify Shipping Address Fields: Maps shipping address details, such as:
- Address 1, Address 2, City, Company, Country, Country Code
- First Name, Last Name, Name, Phone
- Province, Province Code, Zip
- Latitude, Longitude
What Can Be Used (Mapping Options) For each field, you can choose how to handle your Shopify data with these options:
- Don’t Map: Skip the field entirely. It won’t be sent to JM Wholesale (e.g., ignoring “Latitude” if not needed).
- Set To Empty: Send an empty value for the field (e.g., setting “Address 2” to empty).
- Field / Direct Copy: Copy the data directly from your Shopify order (e.g., copying Shopify’s “address1” to JM Wholesale’s “Address 1”).
- Value: Set a specific value for the field (e.g., setting “Country” to “United States” for all orders).
- Mapping Set: Apply a transformation to the data (e.g., formatting the phone number).
- Rules: Use conditional logic to process the data (e.g., “If Country is US, set Country Code to ‘US’”). This is optional and can be skipped if you’re new to mapping.
Required Fields While the template doesn’t mark fields as required, certain fields are typically essential for JM Wholesale to process purchase orders:
- SKU (Line Item): Must be mapped to identify the products being ordered.
- Quantity (Line Item): Must be mapped to specify the number of items to fulfill.
- Shipping Address Fields (e.g., Address 1, City, Country, Zip): Typically required to ensure JM Wholesale knows where to ship the order.
Ensure these fields are mapped to avoid issues with order processing. Specific Mapping Suggestions Here are suggested mappings for key fields to help you get started with sending fulfillment requests to JM Wholesale. We’ll use Shopify’s field names and map them to JM Wholesale’s requirements.
SKU (Line Item): The unique identifier for the product being ordered.
- Suggested Mapping: Map to Shopify’s “sku” field using “Field / Direct Copy.”
- Reason: Ensures JM Wholesale can identify the exact product to fulfill. This field is essential.
- Example: If Shopify’s SKU is “JM12345-V1,” this will be sent to JM Wholesale.
Quantity (Line Item): The number of items to fulfill.
- Suggested Mapping: Map to Shopify’s “quantity” field using “Field / Direct Copy.”
- Reason: Specifies how many units JM Wholesale should fulfill for each line item. This field is essential.
- Example: A quantity of “3” from Shopify will be sent as the number of items to fulfill.
Price (Line Item): The price per item.
- Suggested Mapping: Map to Shopify’s “price” field using “Field / Direct Copy,” or set to “Don’t Map” if JM Wholesale doesn’t require it.
- Reason: Provides the price per item for JM Wholesale’s reference, if needed.
- Example: A price of “$15.00” from Shopify will be sent for the line item.
Address 1 (Shipping Address): The primary shipping address line.
- Suggested Mapping: Map to Shopify’s “address1” field (under shipping_address) using “Field / Direct Copy.”
- Reason: Ensures JM Wholesale knows where to ship the order. This field is typically required.
- Example: “123 Main St” from Shopify will be sent as the shipping address.
City (Shipping Address): The city for the shipping address.
- Suggested Mapping: Map to Shopify’s “city” field (under shipping_address) using “Field / Direct Copy.”
- Reason: Specifies the city for shipping, which is typically required.
- Example: “New York” from Shopify will be sent as the shipping city.
Country (Shipping Address): The country for the shipping address.
- Suggested Mapping: Map to Shopify’s “country” field (under shipping_address) using “Field / Direct Copy,” or set to “United States” using “Value” if all orders ship to the US.
- Reason: Specifies the country for shipping, which is typically required.
- Example: “United States” from Shopify will be sent as the shipping country.
Zip (Shipping Address): The postal code for the shipping address.
- Suggested Mapping: Map to Shopify’s “zip” field (under shipping_address) using “Field / Direct Copy.”
- Reason: Provides the postal code for shipping, which is typically required.
- Example: “10001” from Shopify will be sent as the shipping zip code.
Name (Shipping Address): The recipient’s full name.
- Suggested Mapping: Map to Shopify’s “name” field (under shipping_address) using “Field / Direct Copy,” or combine “first_name” and “last_name” if “name” isn’t available.
- Reason: Identifies the recipient for shipping purposes.
- Example: “John Doe” from Shopify will be sent as the recipient’s name.
Note (Order): Any additional notes for the order.
- Suggested Mapping: Map to Shopify’s “note” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Allows you to include special instructions or notes for JM Wholesale.
- Example: “Please ship ASAP” from Shopify will be sent as an order note.
Tips for Mapping
- Start with the essential fields (SKU, Quantity, Shipping Address fields) to ensure JM Wholesale can process the fulfillment request.
- Use “Direct Copy” for fields like Address 1 or SKU to maintain accuracy between Shopify and JM Wholesale.
- For fields you don’t need to send (e.g., Latitude, Longitude), select “Don’t Map” to simplify the request.
- If most orders ship to a specific country (e.g., US), consider using “Value” to set the Country field consistently.
- Verify with JM Wholesale if they require specific fields (e.g., Phone or Company) to ensure your mapping meets their expectations.
Conclusion
You’ve successfully set up the JM Wholesale Send Fulfillment Requests integration! With your connection established, settings configured, and mapping template in place, you’re now ready to send purchase orders to JM Wholesale seamlessly. This integration will streamline your fulfillment process, ensuring orders are processed accurately and efficiently. If you encounter any issues or need further assistance, feel free to reach out to your support team. Happy fulfilling!
Get Shipments
Supported | JM Wholesale - Get Shipments
Introduction to JM Wholesale Get Shipments Integration
Welcome to the JM Wholesale Get Shipments integration guide! This section will guide you through the process of connecting to JM Wholesale to retrieve shipment information for your fulfilled orders. Whether you’re new to shipment integrations or an experienced user, we’ll walk you through each step—from establishing the connection to mapping shipment data—so you can keep your order tracking up to date. Let’s get started!
Purpose of This Integration
The JM Wholesale Get Shipments integration allows you to fetch shipment details from JM Wholesale, such as tracking numbers and shipping methods, to update your system with the latest fulfillment information. This integration:
- Retrieves shipment data, including tracking numbers, carriers, and shipping costs, from JM Wholesale.
- Maps this data to your system’s shipment fields for seamless integration with your order management.
- Keeps your customers informed with accurate tracking information for their orders.
This integration ensures you have the latest shipment details, streamlining your order tracking process and improving customer satisfaction. How the Integration Works
The JM Wholesale Get Shipments integration follows a structured process to retrieve and integrate shipment data into your system:
1. Connecting to JM Wholesale: Establishes a connection with JM Wholesale’s system. No additional connection information is required for this integration.
2. Configuring Settings: Allows you to customize how the integration runs, with minimal configuration needed in this case.
3. Mapping Data: Uses a mapping template to align JM Wholesale’s shipment data with your system’s shipment fields (e.g., mapping their tracking number to your Tracking Number field).
4. Running the Integration: Fetches and processes shipment data, either manually or on a schedule, to update your system.
Note: This integration focuses on retrieving shipment details, so mapping the relevant fields (like Tracking Number and Carrier) is key to ensuring your system reflects accurate tracking information. Configuration Options
The JM Wholesale Get Shipments integration requires minimal configuration, as noted in the settings screen: “There are no additional configurations that you need to set up in FIXpoint for this integration.” However, you can customize the following:
- Scheduling: Choose to run the integration manually or schedule it to run automatically (e.g., daily at 6 AM UTC) to keep your shipment data updated.
Setup Instructions
Follow these steps to set up the JM Wholesale Get Shipments integration:
1. Connect the Integration: In your system, navigate to the "Get Shipments" section under "Integrations." Select "JM Wholesale" from the list. You’ll see a message: “No additional connection information is needed for this integration.” Click “Save and Proceed” to continue.
2. Configure Settings: The settings screen will indicate that no additional configurations are needed. However, you can set up scheduling:
- Scheduling: Optionally, enable automatic scheduling (e.g., daily at 6 AM UTC) to retrieve shipment data without manual intervention.
Once reviewed, click “Save and Proceed.” 3. Define a Mapping Template: Create a mapping template to match JM Wholesale’s shipment data to your system’s shipment fields. This ensures the data is imported correctly. We’ll cover this in detail below.
4. Run the Integration: After setting up the mapping template, run the integration manually by clicking “Run Integration” or let it run on your scheduled time.
Mapping Template Overview
A mapping template ensures JM Wholesale’s shipment data aligns with your system’s shipment fields. It defines how their shipment fields (e.g., tracking number, carrier) map to your fields (e.g., Tracking Number, Carrier). Let’s break down what’s covered, how to use it, and provide specific mapping suggestions to help you get started.
Interface Overview
- The mapping screen is labeled “JM Wholesale - Get Shipments” at the top. You can name your template (e.g., “JM Wholesale - Get Shipments 1”).
- There are buttons at the top: Delete (remove the template), Duplicate (create a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Shows options for handling JM Wholesale’s data (e.g., “Field,” “Value,” “Don’t Map”).
- Right Column (To Shipment Field): Lists your system’s shipment fields (e.g., “Tracking Number,” “Carrier”).
What’s Covered in the Mapping Template The mapping template focuses on shipment-level data from JM Wholesale, including:
- Shipment Fields: These are the details for each shipment, such as:
- Carrier: The shipping carrier used (e.g., UPS, FedEx).
- Fulfillment Request Number: The identifier for the associated fulfillment request.
- Method: The shipping method (e.g., Ground, Express).
- Note: Any additional notes about the shipment.
- Shipped At: The date and time the shipment was sent.
- Shipping Cost: The cost of shipping for the shipment.
- Tracking Number: The tracking number for the shipment.
- Tracking URL: The URL to track the shipment.
What Can Be Used (Mapping Options) For each field, you can choose how to handle JM Wholesale’s shipment data with these options:
- Don’t Map: Skip the field entirely. It won’t be imported (e.g., ignoring “Note” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Shipping Cost” to empty).
- Field / Direct Copy: Copy the data directly from JM Wholesale’s shipment data (e.g., copying their tracking number to your Tracking Number field).
- Value: Set a specific value for the field (e.g., setting “Carrier” to “UPS” for all shipments).
- Mapping Set: Apply a transformation to the data (e.g., formatting the Shipped At date).
- Rules: Use conditional logic to process the data (e.g., “If Carrier is ‘UPS’, set Method to ‘Ground’”). This is optional and can be skipped if you’re new to mapping.
Required Fields While the template doesn’t mark fields as required, certain fields are typically essential for effective shipment tracking:
- Tracking Number: Should be mapped to provide tracking information to your customers.
- Fulfillment Request Number: Should be mapped to link the shipment to the correct fulfillment request in your system.
Ensure these fields are mapped to avoid gaps in tracking information. Specific Mapping Suggestions Here are suggested mappings for key fields to help you get started with retrieving shipment data from JM Wholesale. Since the exact field names from JM Wholesale’s data aren’t specified, we’ll assume typical field names (e.g., “tracking_number,” “carrier”) and guide you on how to map them to your system. Adjust these based on the actual field names in JM Wholesale’s data.
Tracking Number: The tracking number for the shipment.
- Suggested Mapping: Map to JM Wholesale’s “tracking_number” or “TrackingNumber” field using “Field / Direct Copy.”
- Reason: Provides the tracking number to update your system and inform customers. This field is essential.
- Example: If JM Wholesale’s tracking number is “1Z9999W99999999999,” this will be imported as the Tracking Number.
Fulfillment Request Number: The identifier for the associated fulfillment request.
- Suggested Mapping: Map to JM Wholesale’s “fulfillment_request_number” or “OrderID” field using “Field / Direct Copy.”
- Reason: Links the shipment to the correct fulfillment request in your system, ensuring accurate tracking. This field is essential.
- Example: A fulfillment request number of “FR12345” from JM Wholesale will be imported to match the corresponding request.
Carrier: The shipping carrier used for the shipment.
- Suggested Mapping: Map to JM Wholesale’s “carrier” or “CarrierName” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Identifies the carrier for tracking and reporting purposes.
- Example: If JM Wholesale’s carrier is “UPS,” this will be imported as the Carrier.
Method: The shipping method used.
- Suggested Mapping: Map to JM Wholesale’s “shipping_method” or “Method” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Specifies the shipping method (e.g., Ground, Express) for reference.
- Example: A method of “Ground” from JM Wholesale will be imported as the Method.
Shipped At: The date and time the shipment was sent.
- Suggested Mapping: Map to JM Wholesale’s “shipped_at” or “ShipmentDate” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Records when the shipment was sent, useful for tracking timelines.
- Example: A shipped date of “2025-04-20T14:30:00Z” from JM Wholesale will be imported as the Shipped At date.
Tracking URL: The URL to track the shipment.
- Suggested Mapping: Map to JM Wholesale’s “tracking_url” or “TrackingURL” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Provides a direct link for tracking, enhancing customer experience.
- Example: A tracking URL of “https://www.ups.com/track?tracknum=1Z9999W99999999999” from JM Wholesale will be imported.
Shipping Cost: The cost of shipping for the shipment.
- Suggested Mapping: Map to JM Wholesale’s “shipping_cost” or “ShippingCost” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Tracks the shipping cost for accounting and reporting purposes.
- Example: A shipping cost of “$10.50” from JM Wholesale will be imported.
Note: Any additional notes about the shipment.
- Suggested Mapping: Map to JM Wholesale’s “note” or “Comments” field using “Field / Direct Copy,” or set to “Don’t Map” if not needed.
- Reason: Captures any special instructions or comments about the shipment.
- Example: A note of “Handle with care” from JM Wholesale will be imported as the Note.
Tips for Mapping
- Start with the essential fields (Tracking Number, Fulfillment Request Number) to ensure your system can track shipments effectively.
- Use “Direct Copy” for fields like Tracking Number and Carrier to maintain accuracy between JM Wholesale and your system.
- For fields you don’t need (e.g., Shipping Cost, Note), select “Don’t Map” to simplify the data import.
- Review JM Wholesale’s shipment data to confirm the exact field names (e.g., “tracking_number” vs. “TrackingNumber”) and adjust mappings accordingly.
- If JM Wholesale provides inconsistent date formats for Shipped At, consider using a Mapping Set to standardize the format in your system.
Conclusion
You’ve successfully set up the JM Wholesale Get Shipments integration! With your connection established, settings configured, and mapping template in place, you can now retrieve shipment details from JM Wholesale seamlessly. Your system will stay updated with accurate tracking information, improving your order management and keeping your customers informed. If you encounter any issues or need further assistance, feel free to reach out to your support team. Happy tracking!