The mapping template for ShipStation’s Get Inventory [Primary] integration tells Flxpoint how to import your product data. Here’s what you need to know:

1. Template Header

• Template Name:
  • Default: “Get Inventory [Primary]”
  • You can rename it to clearly indicate its purpose (e.g., “ShipStation GIP – Standard Mapping”).
• Action Buttons:
  • Delete: Removes the template.
  • Duplicate: Creates a copy for modifications.
  • Save: Saves any changes you’ve made.

2. Section Breakdown

• Inventory Parent Fields:
  • Maps core product data (e.g., SKU, Brand, Category, Description).
• Inventory Variant Fields:
  • Maps attributes for product variants (e.g., size, color, dimensions, weight).

3. Mapping Options for Each Field

For each mapping row, you choose one of these options:

• Don’t Map: The field is ignored.
• Set To Empty: Clears the field in Flxpoint.
• Field: Directly pulls the value from a corresponding ShipStation field.
• Value: Inserts a fixed value.
• Mapping Set: Applies a predefined transformation or lookup.
• Direct Copy: Simply copies the field as is.

A Rules option is also available, click its caret icon to view advanced conditional mapping if needed.

4. Common Fields & Tooltips

• SKU: The unique identifier for each product; crucial for matching products in Flxpoint.
• Name/Title: The product’s display name.
• Brand: If provided, maps to your product’s brand; otherwise, select “Don’t Map.”
• Categories: Up to three category levels (Category 1, 2, and 3) can be mapped if you use them.
• Description / Internal Notes: For product descriptions or internal remarks.
• Cost: Maps the product cost if available.
• Dimensions & Weight:
  • Fields such as Weight (Oz), Height, Length, and Width are available for shipping calculations.
  • Dimension Unit / Weight Unit: Configure one (or the abbreviated version) per field; if both are set, the full unit is prioritized.
• Allow Backorders: Option to mark items as available for backorders (tooltip explains the behavior).
• Identifiers (ASIN, MPN, GTIN, UPC): Map these if your data includes these additional product IDs.
• Master SKU & Reference Identifier:
  • Master SKU: Use if your data includes a primary master SKU to link products.
  • Reference Identifier: An optional value (similar to a UPC or MPN) for matching variants.

5. Custom Fields

• Custom Fields (100) & Custom Aggregate Fields (10):
  • Use these sections for any additional data points not covered by standard fields.

6. Best Practices

• Focus on SKU: This field is critical for product identification.
• Map only what you need: Use “Don’t Map” for irrelevant fields.
• Review tooltips: Hover over any tooltip icons (question marks) to get context on what each field does.
• Test your mapping: After saving, run a test import to ensure data appears as expected.

The Send Fulfillment Requests operation is used to send order information from Flxpoint to ShipStation. This mapping template defines how each field in your order data is translated into the corresponding fields within ShipStation. You’ll typically see columns labeled From Value (Flxpoint data) and To ShipStation Advance Option Field or other ShipStation fields.

1. Template Header and Actions

• Title & Name: Displays “Send Fulfillment Requests” and a text input to name your mapping template.
• Action Buttons:
  • Delete – Removes the template.
  • Duplicate – Creates a copy.
  • Save – Saves changes to the template.

2. Mapping Panel Layout

• Each row shows how a specific Flxpoint order field maps into ShipStation.
• Common fields include billing/shipping addresses, order numbers, and line item details.

3. Mapping Options & Tooltips

• Don’t Map: Ignores this field.
• Set To Empty: Overwrites any existing value with an empty one.
• Field: Directly map a Flxpoint field to ShipStation.
• Value: Enter a fixed/custom value (e.g., always “Free Shipping”).
• Mapping Set: Use a pre-built set of transformations or lookups.
• Rules (Caret Icon): Allows advanced, conditional transformations if needed.

Tooltips next to each option show additional context, such as data types (“Text,” “Number,” or “Key/Value”) or usage notes (e.g., “This field identifies the store in ShipStation”).

4. Optional: Store ID

You may see a Store ID field in the mapping template. This is optional but can be configured if you want to direct orders to a specific store within your ShipStation account. In Flexpoint, the Store ID is typically mapped in the “Send POVR” or “ShipStation advanced mapping” configuration. For example:

×

If you don’t need to differentiate stores in ShipStation, you can simply Don’t Map this field.

5. Why This Mapping Matters

• Accurate Order Data: Ensures that each order’s details (items, shipping addresses, etc.) are properly sent to ShipStation for fulfillment.
• Customizability: Lets you tailor how fields like addresses, SKUs, and shipping methods flow into ShipStation.
• Reduced Errors: Proper mapping avoids manual re-entry or mismatched fields, saving time and preventing fulfillment delays.

6. Best Practices

• Map Critical Fields: Ensure the main order fields—like billing/shipping info and line item SKUs—are correctly mapped.
• Use Tooltips: Hover over question marks or info icons for quick guidance on data types and usage.
• Test & Validate: Send a test order through to confirm your mappings. Adjust if any fields aren’t arriving as expected.
• Keep It Simple: Only map what you need. Use Don’t Map or Set To Empty for irrelevant fields.

This mapping template defines how each field in your ShipStation shipment feed is translated into the corresponding shipment details within Flxpoint. In this template, you’ll see two main columns:

• From Value: The data point coming from ShipStation.
• To [Destination Field]: The Flxpoint shipment field that will store the imported data.

Template Header and Actions

• Title & Name: The header displays the title (e.g. “Get Shipments”) and a text input where you can name your mapping template. This name should clearly indicate that it’s for shipment data.
• Action Buttons: You’ll find options to Delete, Duplicate, and Save your template. These help you manage multiple mapping configurations if needed.
  
   

Mapping Panel Layout

• The template is divided into sections where you map each ShipStation shipment field (like tracking number, carrier, and shipment date) to Flxpoint’s corresponding fields.
• For example, you might map:
  • ShipStation Tracking Number to Flxpoint Shipment Tracking Field
  • ShipStation Carrier to Flxpoint Carrier Field
  • ShipStation Shipment Date to Flxpoint Shipment Date Field
  • Order Number to a field that links the shipment back to its corresponding order in Flxpoint

Mapping Options
For every field, you’ll see a set of options you can select from:

• Don’t Map: Ignores this data point.
• Set To Empty: Clears any existing value.
• Field: Directly maps a ShipStation field to the Flxpoint field.
• Value: Allows you to enter a fixed value if the data is static or needs overriding.
• Mapping Set: For advanced scenarios, you can use pre-configured sets that transform or standardize data.
• Direct Copy: Copies the data as it is from ShipStation into Flxpoint.

Tooltips for Guidance
Each field may include a tooltip (typically represented by a question mark or info icon) that provides additional context about:

• The expected data type (for example, “Number” for cost fields or “Text” for address fields).
• The purpose of the field (for instance, a tooltip on Tracking Number might note that this is used for shipment tracking and updates).
• Any special instructions, such as whether a field is required or if it should remain blank under certain conditions.

Why This Mapping Matters

• Accurate Order Tracking:
  By mapping key shipment details (like tracking numbers and shipment dates), Flxpoint can automatically update order statuses and provide accurate tracking information to your customers.
• Data Consistency:
  Using a defined mapping template ensures that all shipment data is consistently imported, reducing manual errors and streamlining your fulfillment process.
• Customizability:
  If your ShipStation feed includes custom fields (or if your shipment data needs additional transformation), the options such as Mapping Set and Rules let you tailor the import to your business needs.

Best Practices

Prioritize Essential Fields:
Make sure to map critical data, tracking numbers, carriers, shipment dates, and order numbers, to ensure shipments are correctly linked to orders.

Use Tooltips:
Hover over each tooltip to review data type expectations and field usage. This helps avoid misconfiguration and data mismatches.

Test the Mapping:
After configuring your mapping template, run a test import of shipments to verify that data populates correctly in Flxpoint. Adjust the mapping if any fields aren’t coming through as expected.

Keep It Simple:
For most users, mapping only the necessary fields (and leaving others as “Don’t Map” or “Set To Empty”) helps keep your configuration clear and easy to maintain.