Spark Shipping Workflows: Pricing Playbook for Price Adjustments
Use this guide to build pricing workflows with exact labels that match the Edit Workflow UI.
Spark Shipping Workflows: Pricing Playbook for Price Adjustments
Use this guide to build pricing workflows with exact labels that match the Edit Workflow UI.
Who is this for
- Merchants who want to automate pricing by brand, MSRP/COST logic, rounding, and MAP guardrails.
How workflows evaluate
- Conditions are evaluated per product.
- Inside a condition group: AND logic.
- Between condition groups: OR logic.
- If conditions match, actions run in order, top-to-bottom.
- Use “Test Workflow (Dry Run)” to preview a SKU before enabling the workflow.
Quick reference: Fields and operators (exact labels)
-
Condition fields:
- Product SKU
- Product Brand
- Product Suggested Price
- Product MSRP
- Product MAP Cost
- Product Cost
- Product Tags
- Product Total Stock
- Product User Field 1–10
-
Condition operators:
- Equals, Does Not Equal, Contains, Does Not Contain
- Greater Than, Less Than
- Less Than % Difference, Greater Than % Difference (require a numeric modifier)
- Is Known, Is Blank (no value required)
-
Condition value types:
- Value
- Product SKU/Brand/Suggested Price/MSRP/MAP Cost/Cost/User Field 1–10
-
Action target fields:
- Product Brand
- Product Suggested Price
- Product User Field 1–10
-
Action operations:
- Set to Value
- Change by %
- Set To Field
- Set to % Off of Field
- Set to % Markup of Field
- Set to % of Field
- Subtract from Field, Add to Field
- Add Value, Subtract Value
- Round Up Value with Increment
-
Action value_field options:
- Product Brand, Product Suggested Price, Product MSRP, Product MAP, Product Cost, Product User Field 1–10
Notes:
- “Product MAP Cost” (conditions) may appear as “Product MAP” in the action value_field dropdown. Same concept.
- Brand entry supports autocomplete when the condition/value type is set to
Value
forProduct Brand
.
Step-by-step: Building a rule
- Add your conditions
- Click “Add AND Condition within group” to add filters that must all be true.
- Click “Add OR Condition Group” to create alternative sets of filters.
- Add your actions (in order)
- Click “Add Action”.
- Choose a target field (e.g., Product Suggested Price) and operation.
- If the operation uses a base field, choose Value field; if it uses a numeric value, use the Value input; if it needs a % modifier, fill the modifier.
- Save and test
- Click “Save Workflow”.
- Use “Test Workflow (Dry Run)” with a SKU to verify the output.
- Toggle “Active” to enable.
Common pricing recipes
Brand markdown: Set to 80 percent of MSRP for selected brands
- Conditions (use OR groups for multiple brands):
- Group 1: Field = Product Brand, Operator = Equals, Value = ACME
- Group 2: Field = Product Brand, Operator = Equals, Value = Globex
- Action:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 80
- Value field: Product MSRP
- Tip: Use Contains for broader matches (e.g., “BrandX Clearance”).
MAP floor: Never go below MAP
- Conditions:
- Field: Product Suggested Price, Operator: Less Than, Value type: Product MAP Cost
- Action:
- Field: Product Suggested Price
- Operation: Set To Field
- Value field: Product MAP
- Tip: Place MAP guardrails after other price adjustments.
Cost-based markup for a tagged assortment
- Conditions:
- Field: Product Tags, Operator: Contains, Value: wholesale
- Action:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 20
- Value field: Product Cost
- Result: Suggested Price = Cost + (Cost × 20 percent).
Clearance discount off MSRP for brand lines
- Conditions (OR groups):
- Group 1: Product Brand Contains BrandX Clearance
- Group 2: Product Brand Contains BrandY Clearance
- Action:
- Field: Product Suggested Price
- Operation: Set to % Off of Field
- Modifier: 30
- Value field: Product MSRP
Flat fee adjustment on low-cost items
- Conditions:
- Field: Product Cost, Operator: Less Than, Value type: Value, Value: 10
- Action:
- Field: Product Suggested Price
- Operation: Add Value
- Value: 2
- Variation: Use Subtract Value for a flat markdown.
Round to clean price points
- Action 1 (set baseline from MSRP):
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 100
- Value field: Product MSRP
- Action 2 (round):
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00 (use 0.50 for half-dollar increments)
Trigger by percent difference between fields (MSRP vs Cost)
- Conditions:
- Field: Product MSRP
- Operator: Greater Than % Difference
- Modifier: 40
- Value type: Product Cost
- Action:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 75
- Value field: Product MSRP
Additional recipes: MAP and operational examples
MAP percent off retail test (with MAP floor)
- Note: Suggested trigger/context: Product costs changed. Leave Inactive until tested.
- Actions:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 90
- Value field: Product MSRP
- Pair with MAP floor (guardrail) below to avoid under-MAP.
MAP Overrides (tag-based exception to MAP floor)
- Option A (recommended): Exempt certain products from the MAP floor using a tag.
- Edit your MAP floor workflow’s condition and add:
- Field: Product Tags
- Operator: Does Not Contain
- Value type: Value
- Value: map_override
- This ensures the guardrail doesn’t apply when the override tag is present.
- Edit your MAP floor workflow’s condition and add:
- Option B: Create a specific override workflow that runs before the guardrail.
- Conditions:
- Product Tags Contains map_override
- Actions:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 85
- Value field: Product MSRP
- Conditions:
MAP percent off retail (with MAP floor)
- Note: Suggested trigger/context: Product costs changed. Active after testing.
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Off of Field
- Modifier: 10
- Value field: Product MSRP
- Pair with MAP floor (guardrail) to keep price ≥ MAP.
Add 25 percent markup over product cost
- Note: Suggested trigger/context: Product costs changed. Active after testing.
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 25
- Value field: Product Cost
Update at stock change: high-stock clearance
- Note: Suggested trigger/context: Stock changes.
- Conditions:
- Field: Product Total Stock
- Operator: Greater Than
- Value type: Value
- Value: 20
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Off of Field
- Modifier: 20
- Value field: Product MSRP
Push MAP metafield (via user field)
- Note: The workflow editor writes to product fields; pushing to a storefront metafield is handled in channel/integration settings.
- Actions (in workflow):
- Field: Product User Field 1
- Operation: Set To Field
- Value field: Product MAP
- Then map
Product User Field 1
to the desired Shopify metafield in your channel settings.
Distributor-specific recipes (Turn 14, Ingram Micro, TD SYNNEX)
Note: To target a distributor, use either Product Tags (e.g., turn14
, ingram
, synnex
) or a Product User Field (e.g., Product User Field 1
Equals Turn14
).
8. Turn 14: 15 percent off MSRP for AFE and Sparco, rounded to .99
- Conditions:
- Group 1: Product Tags Contains turn14 AND Product Brand Equals AFE
- OR Group 2: Product Tags Contains turn14 AND Product Brand Equals Sparco
- Actions:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 85
- Value field: Product MSRP
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
- Tip: Pair with the “MAP floor” recipe to avoid under-MAP pricing.
9. Turn 14: MSRP missing → Cost + 35 percent with .99 rounding
- Conditions:
- Product Tags Contains turn14
- Product MSRP Is Blank
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 35
- Value field: Product Cost
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
10a. Ingram Micro: Cost under $50 → plus 25 percent
- Conditions:
- Product Tags Contains ingram
- Product Cost Less Than
- Value type: Value
- Value: 50
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 25
- Value field: Product Cost
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
10b. Ingram Micro: Cost ≥ $50 → plus 15 percent
- Conditions:
- Product Tags Contains ingram
- Product Cost Greater Than
- Value type: Value
- Value: 50
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 15
- Value field: Product Cost
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
11. TD SYNNEX: Logitech 12 percent off MSRP with .99 rounding
- Conditions:
- Product Tags Contains synnex
- Product Brand Equals Logitech
- Actions:
- Field: Product Suggested Price
- Operation: Set to % of Field
- Modifier: 88
- Value field: Product MSRP
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
12. TD SYNNEX: HP SKUs cost plus 18 percent with .99 rounding
- Conditions:
- Product Tags Contains synnex
- Product SKU Contains HP-
- Actions:
- Field: Product Suggested Price
- Operation: Set to % Markup of Field
- Modifier: 18
- Value field: Product Cost
- Field: Product Suggested Price
- Operation: Round Up Value with Increment
- Value: 1.00
- Field: Product Suggested Price
- Operation: Subtract Value
- Value: 0.01
13. Turn 14: Low-stock surcharge
- Conditions:
- Product Tags Contains turn14
- Product Total Stock Less Than
- Value type: Value
- Value: 5
- Action:
- Field: Product Suggested Price
- Operation: Add Value
- Value: 5.00
Best practices
- Order matters: put guardrail rules (e.g., MAP) after adjustments.
- Keep rules specific: isolate brands, tags, and catalogs with precise conditions.
- Test first: always use Dry Run on representative SKUs before activating.
- Document intent: add one workflow per clear pricing policy for easier maintenance.
Troubleshooting
- No value field showing? Operators “Is Known/Is Blank” intentionally hide the value area.
- % operators missing a number? “% Difference” (conditions) and “% of/markup/off” (actions) require a numeric modifier.
- Comparing two fields in a condition? Set the value type to the comparison field (not Value).
- Rounding not applying? Ensure the increment is set in the Value input on the rounding action.
Appendix: Exact labels at a glance
- Conditions: “Add AND Condition within group”, “Add OR Condition Group”, “Remove” (trash icon)
- Actions: “Add Action”, “Remove” (trash icon)
- Save/Status: “Save Workflow”, “Active” toggle
- Testing: “Test Workflow (Dry Run)”, label: “Product SKU”, button: “Run Test”
© Spark Shipping. All rights reserved.