ShipStation as WMS/Shipping

Table of Contents

How to Connect Product Operations Order Operations

This guide dives into advanced setup options for connecting ShipStation to flxpoint, offering greater customization for data mapping and sync precision. It details enhanced features such as quantity tracking and v2 API credential integration, alongside comprehensive configuration of sources, orders, and shipments. This documentation empowers you to fine-tune your integration to meet more complex business needs.

How to Connect

Step 1: Log into your Flxpoint account and navigate to the Sources tab.

Step 2: Click on Configure Single Source (or + Add Source) to begin creating a new source.

Step 3: Fill in your source details (vendor, fulfillment, shipping, location). Once completed, click Save.

Step 4: Immediately after saving your source, the connection process begins. Select ShipStation from the list of available integrations.

Step 5: In the connection form, enter your Connection Name, API Key, and API Secret from your ShipStation account.

If you plan to use GIP integration to fetch inventory, an additional “V2 Key” field may be present. Hover over the tooltip to see:
“Only required for GIP integration to fetch inventory. Inventory API add-on must be enabled on your ShipStation account to access this. More details at: docs.shipstation.com/getting-started/”

Step 6: After testing your credentials (Test Connection), continue with the connection process:

Step 7: Review all settings and finalize additional options (e.g., warehouse mappings). Click Save/Done to complete and activate your ShipStation integration.

Step 8: Your integration is now active. Flxpoint will begin importing product data via Get Inventory [Primary]. Additional operations such as Send Fulfillment Requests and Get Shipments can be configured as needed.

ShipStation API V2 Enhancements:

As of 2025, ShipStation offers API V2 options for improved data retrieval:

GIP: An API V2 Key can be added in the connection card to access inventory/quantity data. Both V1 and V2 credentials are validated; with V2, an optional quantity field is enabled on GIP mapping templates. If the API V2 key is not configured, quantity defaults to 0.

Refer to the latest ShipStation API documentation for more details on these enhancements.

Product Operations

The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, like focusing on specific products or updates.

Get Inventory (Primary)

ShipStation - Get Inventory [Primary] (Pro)

This Pro-level operation pulls product data from ShipStation via its V2 API, ensuring real-time updates for SKUs, pricing, and quantity in Flxpoint. By connecting with your valid APIv2 credentials, you can retrieve “On Hand Quantity” automatically—no more manual updates!

Note: The Quantity field only appears if your ShipStation integration uses APIv2 credentials. If you do not see any available quantity, please confirm you have ShipStation V2 enabled.

Mapping Template Overview

In Flxpoint Pro, you have full control over how ShipStation fields map to Inventory Parent and Inventory Variant records. For each field, you can choose:

Don’t Map – Ignore the field entirely.
Set To Empty – Force the field to be blank.
Field – Directly copy from a ShipStation field (e.g., “SKU” → “Parent SKU”).
Value – Use a fixed/custom value for all products.
Mapping Set – Apply a predefined transformation (e.g., brand code conversions).
Rules – Conditional logic (e.g., “If Category = ‘Accessories’, then Type = ‘Accessory’”).

Below is a summary of commonly mapped fields you’ll see in ShipStation’s product feed:

1. Parent-Level Fields

Parent SKU – Often mapped from ShipStation Product.SKU.
All Attributes – “Direct Copy” if you want all available product attributes from ShipStation.
Brand – Can map from ShipStation Product Category.Name if you track brand that way.
Category1 / Category2 / Category3 – Use Don’t Map or map from ShipStation Product Category, depending on your store’s category needs.
Description – Could be mapped from ShipStation Product.Name or ShipStation Product.Internal Notes, depending on how you store descriptive text.
Title – Typically from ShipStation Product.Name, if you want a shorter product title.

2. Variant-Level Fields

SKU – “ShipStation Product.SKU.” If you don’t need separate variants, you can set this to Don’t Map.
Cost – Can map from Default Cost or Average Cost in ShipStation.
GTIN / UPC – If ShipStation has a UPC, you can map it here.
Quantity – Maps from On Hand Quantity (ShipStation Product).
Requires ShipStation APIv2. If you’re not on APIv2, quantity won’t populate.
Allow Backorders / Archived / Bin Location – Often set to Don’t Map unless you have data for these.
Dropship Fee – “Don’t Map” unless you charge a per-item fee and store it in ShipStation.
MAP / MPN / Reference Identifier – “Don’t Map” or “Field” if you have these details in ShipStation.
Shipping Cost / Source List Price – “Field” if ShipStation provides them, or “Don’t Map” otherwise.
Weight – Typically from ShipStation Product.Weight (Oz). You can also set Weight Unit or Weight Unit (Abbreviated) (lb, oz, g, kg).
Height / Length / Width – Map from the respective numeric fields if you need dimensional data.

Advanced transformations—like “Rules” or “Mapping Sets”—are available in Pro, allowing you to:

Automatically categorize items by brand, product type, or custom tags.
Apply conditional logic (e.g., “If Cost > 100 then set MAP to Cost + 20”).
Use static or formula-based values for specialized fields.

Common Issues & Tips

Quantity Missing: If your “Quantity” is always zero or not visible, confirm you’ve upgraded to ShipStation’s APIv2 in your Flxpoint connection.
Mapping Mistakes: Double-check that you didn’t accidentally map the wrong ShipStation field (e.g., SKU vs. Price). For parent-level fields, confirm you’re referencing “ShipStation Product” or “ShipStation Product Category” as needed.
Partial Data: If a field is blank in Flxpoint, verify ShipStation actually populates that data (e.g., Default Cost, Height, Width, etc.).
Advanced Rules: In Pro, you can create conditional logic or use Mapping Sets to transform values. If you see unexpected data, review your rules or transformations.

Once configured, Flxpoint will parse and update your product catalog automatically. Be sure to test your mapping template and confirm each field’s data flow before finalizing.

Order Operations

These operations submit orders to vendors for fulfillment and then import shipment details, linking order processing to shipment tracking.

Send Fulfillment Requests

Supported

Send Fulfillment Requests pushes your order details from Flxpoint to ShipStation for streamlined fulfillment. It maps addresses, items, and shipping info to the correct fields in ShipStation, reducing errors and speeding up processing. Once configured, orders flow seamlessly into ShipStation. This automation saves time and ensures more accurate shipments.

Ship Station Send Fulfillment Request Mapping Template

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.

Get Shipments

Supported

Get Shipments pulls tracking and shipping updates from ShipStation back into Flxpoint. It automatically attaches carrier info, tracking numbers, and shipment statuses to the relevant orders. You gain real-time visibility into fulfillment progress, keeping customers informed and reducing manual data entry. With this operation, your shipping information stays current at all times.

Ship Station Get Shipmens Mapping Template

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.

Flxpoint Knowledge