This document provides a comprehensive guide to integrating with the ALMS Marketplace, enabling seamless inventory management, order fulfillment, and shipment tracking. It covers key processes such as retrieving inventory data, sending orders, and syncing shipment details, ensuring your system stays updated with accurate product, pricing, and tracking information. Whether you're new to marketplace integrations or an experienced user, this guide will help you configure connections, map data fields, and troubleshoot issues effectively.
How to Connect
Step 1: Log into your Flxpoint account and navigate to the Connections tab, then select Fulfillment Sources.
Step 2: Under the Sources section, click on + Add Source to begin creating a new source for your ALMS Marketplace connection.
Step 3: In the Create Source popup, enter the source name as "ALMS Marketplace" and select the appropriate type from the dropdown. Click Save.
Step 4: After saving, you’ll see a message: "You have not created any integrations yet." Click Get Started to set up the integration.
Step 5: In the Setup Integrations popup, select Flx Supplier Directory (recommended) to proceed with the ALMS Marketplace integration.
Step 6: In the Let's Find Your Supplier popup, search for "ALMS Marketplace" in the Search Suppliers field. Select ALMS Marketplace from the list and click Select.
Step 7: In the Confirm Your Relationship With Supplier popup, check the box to confirm that you have a reseller account with ALMS Marketplace. Click Continue.
Step 8: In the Authenticate With Supplier popup, enter the following details provided by ALMS Marketplace:
Feed URL: [Enter the URL to retrieve the ALMS Marketplace API for GET Inventory (Primary) and GET Inventory (Secondary)]
API Token: Enter the API token required for Send Fulfillment Requests and GET Shipments. This token is used to authenticate with the ALMS Marketplace.
How to Obtain the API Token: Log into your ALMS Marketplace account, navigate to the Settings or API Access section, and generate or copy your API token. If you don’t have access, contact ALMS Marketplace support to request the token.
Click Continue to proceed.
Step 9: In the Master SKU section, set up your SKU mapping (Inventory SKU → Master SKU → Listing SKU). Optionally, set an SKU prefix (e.g., "ALMS-") if needed. Click Save to complete the basic setup.
Step 10: To enable Send Orders and Get Shipments, ensure the integration is properly set up using the provided Feed URL. In the Send Orders and Get Shipments sections, enable Automatically Send Orders and Automatically Get Shipments. Click Save to complete the setup.
×
![]()
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 and Pricing & Quantity
Supported | ALMS Marketplace - Get Inventory and Pricing & Quantity
Introduction to ALMS Marketplace Get Inventory and Pricing & Quantity Integration
This guide provides a comprehensive overview of the ALMS Marketplace Get Inventory and Pricing & Quantity integration, designed to retrieve inventory data, including pricing and quantity details, from ALMS Marketplace and sync it with your system. This integration combines the functionality of primary and secondary inventory retrieval with pricing and quantity updates, allowing you to manage product data, variants, and stock levels efficiently. Whether you're new to inventory management or an experienced user, this section will guide you through connecting to ALMS Marketplace via API, configuring settings, and mapping inventory data into your system. Let’s dive into the setup and configuration process.
Purpose of This Integration
The ALMS Marketplace Get Inventory and Pricing & Quantity integration is designed to fetch and update inventory data, including pricing and stock quantities, from ALMS Marketplace. This integration:
- Retrieves primary inventory data (e.g., product title, description, categories) and secondary variant-level data (e.g., SKU, cost, MAP, MSRP, quantity, shipping costs).
- Updates pricing and quantity fields for inventory variants, ensuring accurate stock and cost information.
- Supports master SKU mapping to link inventory SKUs to product and listing SKUs in your system.
- Optionally creates new variants if enabled in the settings.
This ensures your inventory, pricing, and quantity data remain accurate and synchronized with ALMS Marketplace. How the Integration Works
The integration follows a structured process to retrieve and update inventory, pricing, and quantity data from ALMS Marketplace:
1. Connecting to Data Sources: Establishes a connection to ALMS Marketplace using a Feed URL for inventory data retrieval.
2. Retrieving Data: Fetches primary inventory data (e.g., product attributes, images) and secondary variant-level data (e.g., SKU, cost, quantity) via the provided Feed URL.
3. Parsing Data: Interprets the API response data into structured formats for processing.
4. Processing & Mapping: Maps the retrieved data to your system’s inventory fields using a mapping configuration, with the ability to enable or disable specific fields (e.g., mapping "Price" to "Cost").
5. Updating Data: Updates existing products and variants with the new data or creates new variants if enabled, applying master SKU mappings as configured.
Note: You’ll need a Feed URL from ALMS Marketplace to access their inventory data. If you don’t have one, contact your support team for assistance. Configuration Options
You can customize the integration with the following settings:
- Feed URL: The ALMS Marketplace Feed URL for retrieving inventory data (required for both primary and secondary inventory retrieval).
- Master SKU Mapping: Define how SKUs are mapped between Inventory SKU, Master SKU, and Listing SKU. You can also set a SKU prefix if needed.
- Automatically Pricing & Quantity: Enable or disable automatic updates for pricing and quantity fields (default: Enabled).
- Allow Create Variant: Enable or disable the creation of new variants during the integration run (default: Disabled).
- Scheduling: Set the integration to run manually or on a schedule (e.g., daily at 8 AM UTC).
Setup Instructions
Follow these steps to configure the ALMS Marketplace Get Inventory and Pricing & Quantity integration:
1. Connect the Integration: Navigate to the "Get Inventory" section and select "ALMS Marketplace." Configure the connection by providing:
- Feed URL: Enter the Feed URL provided by ALMS Marketplace for inventory retrieval.
Test the connection to ensure it works, then save it. If you don’t have a Feed URL, contact your support team for assistance. 2. Configure Master SKU Mapping: Set up the SKU mapping flow:
- Define the mapping from Inventory SKU to Master SKU to Listing SKU.
- Optionally set a SKU prefix to standardize SKU formats.
3. Configure Pricing & Quantity Settings: Adjust the following options:
- Enable or disable Automatically Pricing & Quantity to control whether pricing and quantity updates are applied automatically.
- Enable or disable Allow Create Variant based on whether you want new variants to be created during the integration run.
4. Define Mapping Configuration: Configure how ALMS Marketplace’s data maps to your system’s fields, with the ability to enable or disable specific fields. This step is detailed below.
5. Run the Integration: Start the integration manually or let it run on your configured schedule.
Data Sources
The integration retrieves data directly from the ALMS Marketplace API via the provided Feed URL, which includes:
- Primary Inventory Data: Product Title, Description, Brand, Category 1, Category 2, Category 3, All Attributes, All Custom Fields, All Images, All Options, Parent SKU.
- Secondary Inventory Data (Variants): SKU, Master SKU, Cost, MAP, MSRP, Quantity, Shipping Cost, Height, Length, Width, Weight, Dimension Unit, Weight Unit, UPC, GTIN, MPN, ASIN, Title, All Images, All Options.
Mapping Configuration Details
The mapping configuration defines how ALMS Marketplace’s inventory data is mapped to your system’s inventory fields, with the ability to enable or disable specific fields to control what data is imported. This section explains how to set up and use the mapping configuration, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “ALMS Marketplace → FIXpoint” and is divided into sections like “Get Inventory” and “Get Pricing & Quantity.”
- Each section lists fields available from ALMS Marketplace (e.g., “Price,” “Quantity”) and their corresponding mappings to your system (e.g., “Inventory Variant: Cost,” “Inventory Variant: Quantity”).
- Each field has a toggle to enable or disable it:
- Enabled: The field will be imported and updated in your system.
- Disabled: The field will be ignored, preventing import or syncing.
- Required fields (e.g., SKU, Master SKU) cannot be disabled and are marked as “Required.”
Mapping Options For each field, you can toggle whether to import the data:
- Enable: Imports the data into your system (e.g., enabling “Price” to update “Inventory Variant: Cost”).
- Disable: Ignores the field, preventing import or syncing (e.g., disabling “MAP” to skip updating MAP prices).
Note: Required fields like SKU and Master SKU cannot be disabled. Available Source Fields The following fields are available from ALMS Marketplace’s API for mapping to your system’s inventory fields:
- Inventory Parent Fields: Title, Description, Brand, Category 1, Category 2, Category 3, All Attributes, All Custom Fields, All Images, All Options, Parent SKU.
- Inventory Variant Fields: SKU, Master SKU, Cost, MAP, MSRP, Quantity, Shipping Cost, Height, Length, Width, Weight, Dimension Unit, Weight Unit, UPC, GTIN, MPN, ASIN, Title, All Images, All Options.
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations and suggested settings:
Inventory Parent Fields:
Title: The title of the product.
- Source: Product Title (Text).
- Example: “Wireless Headphones”
- Target: Inventory Parent: Title
- Suggested Setting: Enable to import the product title.
- Reason: Ensures the product title is updated in your system.
Description: The description of the product.
- Source: Description (Text).
- Example: “High-quality wireless headphones with noise cancellation.”
- Target: Inventory Parent: Description
- Suggested Setting: Enable to import the product description.
- Reason: Provides detailed product information for your system.
Brand: The brand of the product.
- Source: Manufacturer (Text).
- Example: “TechBrand”
- Target: Inventory Parent: Brand
- Suggested Setting: Enable to import the brand.
- Reason: Categorizes products by brand in your system.
Parent SKU: The SKU for the parent product.
- Source: Product SKU (Text).
- Example: “HEADPHONE123”
- Target: Inventory Parent: Parent SKU
- Suggested Setting: Required (cannot be disabled).
- Reason: Uniquely identifies the parent product in your system.
Inventory Variant Fields (Pricing & Quantity):
SKU: The unique identifier for the variant.
- Source: SKU (Text).
- Example: “ALM123-V1”
- Target: Inventory Variant: SKU
- Suggested Setting: Required (cannot be disabled).
- Reason: Ensures your system can uniquely identify each variant.
Master SKU: The master SKU linking variants to products.
- Source: SKU (Text).
- Example: “HEADPHONE123”
- Target: Inventory Variant: Master SKU
- Suggested Setting: Required (cannot be disabled).
- Reason: Links variants to the parent product via the master SKU mapping.
Cost: The cost price of the variant.
- Source: Price (Number).
- Example: “15”
- Target: Inventory Variant: Cost
- Suggested Setting: Enable to import the cost price.
- Reason: Updates the cost for pricing calculations at the variant level.
MAP: The minimum advertised price for the variant.
- Source: Map (Number).
- Example: “20”
- Target: Inventory Variant: MAP
- Suggested Setting: Enable to import the MAP price.
- Reason: Ensures compliance with minimum pricing rules for the variant.
MSRP: The manufacturer’s suggested retail price for the variant.
- Source: Msrp (Number).
- Example: “25”
- Target: Inventory Variant: MSRP
- Suggested Setting: Enable to import the MSRP.
- Reason: Provides the suggested retail price for the variant.
Quantity: The available stock quantity for the variant.
- Source: Quantity (Number).
- Example: “50”
- Target: Inventory Variant: Quantity
- Suggested Setting: Enable to import the stock quantity.
- Reason: Updates your system with current stock levels for the variant.
Shipping Cost: The estimated shipping cost for the variant.
- Source: Estimated Shipping Cost (Number).
- Example: “10”
- Target: Inventory Variant: Shipping Cost
- Suggested Setting: Enable to import the shipping cost.
- Reason: Provides accurate shipping costs for the variant.
Practice Mapping To understand how mapping works, try enabling or disabling the “Cost” field for your inventory variant:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the Feed URL for ALMS Marketplace is correct and accessible.
- Ensure your master SKU mapping is correctly set up to link Inventory SKU, Master SKU, and Listing SKU.
- Check that required fields like SKU and Master SKU are enabled in the mapping configuration.
- Confirm that the “Automatically Pricing & Quantity” setting is enabled if you want to update pricing and quantity fields.
- Verify that the “Allow Create Variant” setting aligns with your needs (e.g., disable if you don’t want new variants created).
If the issue persists, contact your support team for assistance. Conclusion
With your mapping configuration set and the integration running, you can now seamlessly retrieve and update inventory, pricing, and quantity data from ALMS Marketplace. Your product catalog will stay synchronized with accurate stock levels, pricing details, and variant information, ensuring efficient inventory management. You’re ready to streamline your inventory and pricing updates with ease!
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 Order
Supported | ALMS Marketplace - Send Orders
Introduction to ALMS Marketplace Send Orders Integration
This guide provides a detailed overview of the ALMS Marketplace Send Orders integration, designed to send orders from your system (FIXpoint) to ALMS Marketplace for fulfillment. This integration automates the process of submitting order details, including shipping and billing addresses, order items, and shipping methods, ensuring seamless communication with ALMS Marketplace. Whether you're new to order fulfillment or an experienced user, this section will guide you through connecting to ALMS Marketplace via API, configuring settings, and mapping order data to the required format. Let’s get started with the setup process.
Purpose of This Integration
The ALMS Marketplace Send Orders integration enables you to send orders to ALMS Marketplace, ensuring efficient fulfillment. This integration:
- Automates the submission of order details, including shipping address, billing address, items, and shipping methods.
- Maps your system's order data to ALMS Marketplace’s required format for order submission.
- Supports automatic order sending with an option to toggle this feature on or off.
This ensures accurate and timely order submission to ALMS Marketplace, reducing manual effort and errors. How the Integration Works
The integration follows a structured process to send orders to ALMS Marketplace:
1. Connecting to Data Sources: Establishes a connection to ALMS Marketplace using the ALMS Marketplace Order API with an API token.
2. Retrieving Order Data: Pulls order data from your system, including shipping and billing addresses, items, and shipping methods.
3. Mapping Data: Maps the order data to ALMS Marketplace’s required format using a mapping configuration, with the ability to enable or disable specific fields (e.g., mapping "Order: Reference Number" to "Fulfillment Request Number").
4. Sending Orders: Submits the mapped orders to ALMS Marketplace via API, either automatically (if enabled) or manually.
5. Confirmation: Logs the sent orders and updates your system with the status.
Note: You’ll need an API token from ALMS Marketplace to send orders. If you don’t have one, contact your support team for assistance. Additionally, ALMS Marketplace requires a separate connection for the Send Orders operation, but you can opt to use the same connection as the Get Shipments operation if applicable. Configuration Options
You can customize the integration with the following settings:
- API Token: The ALMS Marketplace API token for authentication (required for sending orders).
- Use Same Connection as Get Shipments: Option to reuse the same API connection as the Get Shipments operation (default: Disabled).
- Automatically Send Orders: Enable or disable automatic sending of orders to ALMS Marketplace (default: Enabled).
- Scheduling: Set the integration to run manually or on a schedule (e.g., hourly at the start of each hour, UTC).
Setup Instructions
Follow these steps to configure the ALMS Marketplace Send Orders integration:
1. Connect the Integration: Navigate to the "Send Orders" section and select "ALMS Marketplace." Configure the connection by providing:
- API Token: Enter the API token provided by ALMS Marketplace for order submission.
- Optionally, enable Use Same Connection as Get Shipments if you want to reuse the connection from the Get Shipments operation.
Test the connection to ensure it works, then save it. If you don’t have an API token, contact your support team for assistance. 2. Configure Settings: Adjust the following options:
- Enable or disable Automatically Send Orders based on whether you want orders to be sent automatically or manually.
- Set a schedule for automatic runs, if desired (e.g., hourly at the start of each hour, UTC).
3. Define Mapping Configuration: Configure how your system’s order data maps to ALMS Marketplace’s required fields, with the ability to enable or disable specific fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Data Sources
The integration uses data from your system (FIXpoint) and sends it to the ALMS Marketplace API. The data includes:
- Order Data: Fulfillment Request Number (Reference Number), Note, Shipping Code (Shipping Text).
- Shipping and Billing Address: Address Line 1, Address Line 2, City, State, State Code, Postal Code, Country, Country Code, Name (Full Name), Company Name, Email, Phone.
- Order Items: SKU, Quantity.
Mapping Configuration Details
The mapping configuration defines how your system’s order data is mapped to ALMS Marketplace’s required order fields for submission, with the ability to enable or disable specific fields to control what data is sent. This section explains how to set up and use the mapping configuration, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “FIXpoint → ALMS Marketplace” and is divided into sections like “Order,” “Order Billing Address,” “Order Item,” and “Order Shipping Address.”
- Each section lists fields available from your system (e.g., “Fulfillment Request Number,” “Shipping Address: City”) and their corresponding mappings to ALMS Marketplace (e.g., “Order: Reference Number,” “Order Shipping Address: City”).
- Each field has a toggle to enable or disable it:
- Enabled: The field will be sent to ALMS Marketplace.
- Disabled: The field will be ignored, preventing it from being sent.
Mapping Options For each field, you can toggle whether to send the data:
- Enable: Sends the data to ALMS Marketplace (e.g., enabling “Fulfillment Request Number” to send as “Order: Reference Number”).
- Disable: Ignores the field, preventing it from being sent (e.g., disabling “Shipping Address: Email” to skip sending email information).
Available Source Fields The following fields are available from your system for mapping to ALMS Marketplace’s order fields:
- Order Fields: Fulfillment Request Number, Note, Shipping Code.
- Shipping and Billing Address Fields: Address Line 1, Address Line 2, City, State, State Code, Postal Code, Country, Country Code, Name, Company Name, Email, Phone.
- Order Item Fields: SKU, Quantity.
Complete Field Mappings Below is a detailed list of key fields you can map to in ALMS Marketplace’s order format, with explanations and suggested settings:
Order Fields:
Reference Number: The unique identifier for the order.
- Source: Fulfillment Request Number (Text).
- Example: “FR12345”
- Target: Order: Reference Number
- Suggested Setting: Enable to send the order identifier.
- Reason: Ensures ALMS Marketplace can uniquely identify each order.
Note: Additional notes for the order.
- Source: Note (Text).
- Example: “Please ship ASAP”
- Target: Order: Note
- Suggested Setting: Enable to send any special instructions.
- Reason: Provides any special instructions for the order.
Shipping Text: The shipping method code.
- Source: Shipping Code (Text).
- Example: “GROUND”
- Target: Order: Shipping Text
- Suggested Setting: Enable to send the shipping method.
- Reason: Specifies the shipping method for the order.
Order Shipping Address Fields:
Address Line 1: The first line of the shipping address.
- Source: Order Shipping Address: Address Line 1 (Text).
- Example: “123 Main St”
- Target: Order Shipping Address: Address Line 1
- Suggested Setting: Enable to send the shipping address.
- Reason: Ensures accurate delivery address for the order.
City: The city for the shipping address.
- Source: Order Shipping Address: City (Text).
- Example: “San Francisco”
- Target: Order Shipping Address: City
- Suggested Setting: Enable to send the city.
- Reason: Ensures accurate delivery address for the order.
State: The state for the shipping address.
- Source: Order Shipping Address: State (Text).
- Example: “California”
- Target: Order Shipping Address: State
- Suggested Setting: Enable to send the state.
- Reason: Ensures accurate delivery address for the order.
Postal Code: The postal code for the shipping address.
- Source: Order Shipping Address: Postal Code (Text).
- Example: “94105”
- Target: Order Shipping Address: Postal Code
- Suggested Setting: Enable to send the postal code.
- Reason: Ensures accurate delivery address for the order.
Country: The country for the shipping address.
- Source: Order Shipping Address: Country (Text).
- Example: “United States”
- Target: Order Shipping Address: Country
- Suggested Setting: Enable to send the country.
- Reason: Ensures accurate delivery address for the order.
Order Item Fields:
SKU: The SKU of an item in the order.
- Source: Order Item: SKU (Text).
- Example: “ALM123”
- Target: Order Item: SKU
- Suggested Setting: Enable to send the item SKU.
- Reason: Identifies the specific product to be fulfilled.
Quantity: The quantity of an item in the order.
- Source: Order Item: Quantity (Number).
- Example: “2”
- Target: Order Item: Quantity
- Suggested Setting: Enable to send the item quantity.
- Reason: Specifies how many units of the product to fulfill.
Practice Mapping To understand how mapping works, try enabling or disabling the “Shipping Address: City” field for your order:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the API connection to ALMS Marketplace is working and that your API token is correct.
- Ensure you have set up a separate connection for the Send Orders operation, or confirm that the “Use Same Connection as Get Shipments” option is correctly configured.
- Check that the “Automatically Send Orders” setting aligns with your needs (e.g., disable if orders are not sending as expected).
- Confirm that required fields like Reference Number and Order Items (SKU, Quantity) are enabled in the mapping configuration.
- Verify that your system’s order data includes all necessary fields (e.g., Shipping Address, Items).
If the issue persists, contact your support team for assistance. Conclusion
With your mapping configuration set and the integration running, you can now seamlessly send orders to ALMS Marketplace. Your orders will be submitted accurately, with the correct shipping, billing, and item details, ensuring efficient fulfillment and a smooth customer experience. You’re ready to automate your order submission process with ease!
Get Shipments
Supported | ALMS Marketplace - Get Shipments
Introduction to ALMS Marketplace Get Shipments Integration
This guide provides a detailed overview of the ALMS Marketplace Get Shipments integration, designed to retrieve shipment data from ALMS Marketplace and update your system (FIXpoint) with tracking and fulfillment details. This integration helps you keep your order fulfillment records up-to-date by pulling shipment information such as tracking numbers, carrier details, and shipped items. Whether you're new to shipment tracking or an experienced user, this section will guide you through connecting to ALMS Marketplace via API, configuring settings, and mapping shipment data into your system. Let’s get started with the setup process.
Purpose of This Integration
The ALMS Marketplace Get Shipments integration allows you to fetch shipment data from ALMS Marketplace, ensuring your system reflects the latest tracking and fulfillment details for orders. This integration:
- Retrieves shipment details, including carrier, method, tracking number, tracking URL, shipping cost, and shipped-at date.
- Processes shipment items, including SKU and quantity.
- Updates your system with shipment data, linking it to the corresponding fulfillment requests using the Return PO Number.
This ensures accurate tracking information and seamless order fulfillment updates for your business. How the Integration Works
The integration follows a structured process to retrieve and process shipment data from ALMS Marketplace:
1. Connecting to Data Sources: Establishes a connection to ALMS Marketplace using the ALMS Marketplace Order API.
2. Retrieving Data: Fetches shipment details, including tracking information, carrier details, and shipped items, linked to fulfillment requests via the Return PO Number.
3. Parsing Data: Interprets the API response data into structured formats for processing.
4. Processing & Mapping: Maps the retrieved data to your system’s shipment fields using a mapping configuration, with the ability to enable or disable specific fields (e.g., mapping "Tracking Number" to "Shipment: Tracking Number").
5. Saving Data: Saves the processed shipment records into your system, linking them to the corresponding orders or fulfillment requests.
Note: ALMS Marketplace requires a separate connection for the Get Shipments operation, but you can opt to use the same connection as the Send Orders operation if applicable. Configuration Options
You can customize the integration with the following settings:
- API Connection: Use a separate connection for Get Shipments or reuse the same connection as the Send Orders operation (default: Enabled for reusing the Send Orders connection).
- Automatically Get Shipments: Enable or disable automatic retrieval of shipment data (default: Enabled).
- Scheduling: Set the integration to run manually or on a schedule (e.g., daily at 8 AM UTC).
Setup Instructions
Follow these steps to configure the ALMS Marketplace Get Shipments integration:
1. Connect the Integration: Navigate to the "Get Shipments" section and select "ALMS Marketplace." Configure the connection by:
- Enabling Use Same Connection as Send Orders Operation to reuse the Send Orders connection, or set up a separate connection if preferred.
Test the connection to ensure it works, then save it. If you don’t have the necessary API credentials, contact your support team for assistance. 2. Configure Settings: Adjust the following options:
- Enable or disable Automatically Get Shipments based on whether you want shipment data to be retrieved automatically or manually.
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
3. Define Mapping Configuration: Configure how ALMS Marketplace’s shipment data maps to your system’s fields, with the ability to enable or disable specific fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Data Sources
The integration retrieves data directly from the ALMS Marketplace API, which includes:
- Shipment Data: Carrier, Method, Note, Return PO Number (Fulfillment Request Number), Shipped At, Shipping Cost, Tracking Number, Tracking URL.
- Shipment Item Data: SKU, Quantity.
Mapping Configuration Details
The mapping configuration defines how ALMS Marketplace’s shipment data is mapped to your system’s shipment fields, with the ability to enable or disable specific fields to control what data is imported. This section explains how to set up and use the mapping configuration, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “ALMS Marketplace → FIXpoint” and is divided into sections like “Shipment” and “Shipment Item.”
- Each section lists fields available from ALMS Marketplace (e.g., “Carrier,” “Tracking Number”) and their corresponding mappings to your system (e.g., “Shipment: Carrier,” “Shipment: Tracking Number”).
- Each field has a toggle to enable or disable it:
- Enabled: The field will be imported into your system.
- Disabled: The field will be ignored, preventing import or syncing.
Mapping Options For each field, you can toggle whether to import the data:
- Enable: Imports the data into your system (e.g., enabling “Tracking Number” to update “Shipment: Tracking Number”).
- Disable: Ignores the field, preventing import or syncing (e.g., disabling “Note” to skip importing shipment notes).
Available Source Fields The following fields are available from ALMS Marketplace’s API for mapping to your system’s shipment and shipment item fields:
- Shipment Fields: Carrier, Method, Note, Return PO Number (Fulfillment Request Number), Shipped At, Shipping Cost, Tracking Number, Tracking URL.
- Shipment Item Fields: SKU, Quantity.
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations and suggested settings:
Shipment Fields:
Fulfillment Request Number: The identifier linking the shipment to a fulfillment request.
- Source: Return PO Number (Text).
- Example: “FR12345”
- Target: Shipment: Fulfillment Request Number
- Suggested Setting: Enable to import the fulfillment request number.
- Reason: Links the shipment to the corresponding fulfillment request in your system.
Carrier: The carrier used for the shipment.
- Source: Carrier (Text).
- Example: “UPS”
- Target: Shipment: Carrier
- Suggested Setting: Enable to import the carrier.
- Reason: Identifies the carrier for tracking and customer updates.
Method: The shipping method used.
- Source: Method (Text).
- Example: “Ground”
- Target: Shipment: Method
- Suggested Setting: Enable to import the shipping method.
- Reason: Specifies the shipping method for the shipment.
Note: Additional notes about the shipment.
- Source: Note (Text).
- Example: “Fragile items, handle with care”
- Target: Shipment: Note
- Suggested Setting: Enable to import any notes.
- Reason: Provides any special instructions or details about the shipment.
Shipped At: The date and time the shipment was sent.
- Source: Shipped At (Date).
- Example: “2025-04-27T14:30:00Z”
- Target: Shipment: Shipped At
- Suggested Setting: Enable to import the shipped date.
- Reason: Updates your system with the shipment dispatch date.
Shipping Cost: The cost of shipping.
- Source: Shipping Cost (Number).
- Example: “15.99”
- Target: Shipment: Shipping Cost
- Suggested Setting: Enable to import the shipping cost.
- Reason: Records the shipping cost for accounting and tracking purposes.
Tracking Number: The tracking number for the shipment.
- Source: Tracking Number (Text).
- Example: “1Z9999W99999999999”
- Target: Shipment: Tracking Number
- Suggested Setting: Enable to import the tracking number.
- Reason: Allows tracking of the shipment and updates for customers.
Tracking URL: The URL to track the shipment.
- Source: Tracking URL (Text).
- Example: “https://www.ups.com/track?tracknum=1Z9999W99999999999”
- Target: Shipment: Tracking URL
- Suggested Setting: Enable to import the tracking URL.
- Reason: Provides a direct link for tracking the shipment.
Shipment Item Fields:
SKU: The SKU of the shipped item.
- Source: SKU (Text).
- Example: “ALM123”
- Target: Shipment Item: SKU
- Suggested Setting: Enable to import the item SKU.
- Reason: Identifies the specific product that was shipped.
Quantity: The quantity of the item shipped.
- Source: Quantity (Number).
- Example: “2”
- Target: Shipment Item: Quantity
- Suggested Setting: Enable to import the quantity.
- Reason: Updates your system with the number of units shipped for the item.
Practice Mapping To understand how mapping works, try enabling or disabling the “Tracking Number” field for your shipment:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the API connection to ALMS Marketplace is working and correctly configured.
- Ensure you have set up a separate connection for the Get Shipments operation, or confirm that the “Use Same Connection as Send Orders Operation” option is correctly configured.
- Check that the “Automatically Get Shipments” setting aligns with your needs (e.g., disable if shipments are not syncing as expected).
- Confirm that required fields like Fulfillment Request Number are enabled in the mapping configuration to link shipments to orders.
- Verify that the ALMS Marketplace API is returning all expected fields (e.g., Tracking Number, Carrier).
If the issue persists, contact your support team for assistance. Conclusion
With your mapping configuration set and the integration running, you can now seamlessly retrieve shipment data from ALMS Marketplace. Your system will stay updated with accurate tracking information, carrier details, and shipped items, ensuring a smooth fulfillment process and improved customer experience. You’re ready to manage your shipment data with ease!