Location: Settings → Multi-Vendor Settings → Vendor Shop Sync Settings → Other Sync Settings
Applies only when: Vendor Store Sync / Vendor Store Connect is enabled for the vendor.
What this setting does
The Vendor Option Adjustment feature lets merchants map/normalize option values (variant options) coming from vendor stores to the values used on the merchant (marketplace) store.
Example: a vendor labels a color as “Brick Red” but the marketplace uses “Red” — this rule automatically converts the vendor value to the marketplace value when the product is imported or synced, producing consistent filters and storefront displays.
Why use it
- Creates uniform option values across multiple vendors (important for product listing consistency).
- Ensures search, filtering, and faceted navigation work correctly (vendors sometimes use different naming conventions).
- Reduces manual cleanup and customer confusion caused by inconsistent variant names (e.g., “Navy Blue”, “Navy”, “Dark Blue”).
Prerequisites & scope
- Vendor Option Adjustment add-on - $15.
- Vendor Store Sync / Vendor Store Connect must be enabled and connected for the vendor(s) to be affected.
- This setting works at the merchant level but the merchant selects which vendor(s) a rule applies to.
- Rules are applied during product import/sync and when vendor updates are allowed (see your Product Update / Sync rules).
- This maps option values (not option names themselves) — e.g., Option = Color, value = Brick Red.
Workflow — How mapping is applied
- Merchant enables Vendor Option Adjustment and adds mapping rules.
- Vendor connects their store and either imports products or product updates are pushed.
- During import or sync, Shipturtle checks option name + value against mapping rules for that vendor.
- If a rule matches, the vendor value is converted to the override value before the product becomes visible on the merchant store (or before filters/indexing).
- If no rule matches, vendor value stays as-is.
Behavioural details & important notes
- Exact matching: Rules typically match exact text (case sensitivity depends on platform implementation). Use consistent capitalization when creating rules.
- Option name must match vendor name: If vendor uses Color but you enter colour, the rule may not match. Add multiple rules for variant spellings or use the exact vendor label.
- Applies per vendor: You can create vendor-specific rules so vendors can keep their internal naming while the marketplace shows the normalized value.
- Order of precedence: If multiple rules could apply (overlapping rules for same vendor + option), the most specific rule (vendor + exact value) should take precedence. Document and test rule ordering.
- Affects filters & search: Once overridden, the normalized value is used by marketplace filters and faceting (improves UX). However, filter indexing may need re-run or wait for the next sync in some setups.
- Does not rename vendor store data: This mapping is applied at the merchant/store level — the vendor’s own store remains unchanged unless vendor chooses to rename their option values there.
- Not for structural changes: This is for value normalization only. It’s not intended to merge different option types (don’t map size values to color, for example).
- If a vendor store has already been synced earlier, and you create or modify Vendor Option Adjustment rules after that, the rules will not apply automatically to existing products.
To apply the updated rules:
Go to:
Vendor Store Sync → Select All Products → Re-Sync
This forces Shipturtle to reprocess the product data and apply all your new option-value mappings correctly.
Common use-cases
- Normalizing colour names across 50+ vendors so customers can filter for a single “Red” category.
- Converting vendor-specific fabric codes (C100, C-100) to readable names (Cotton).
- Harmonizing measurement units or labels (1L, 1000 ml → 1 L).
Best practices
- Audit vendor option names before creating rules — export sample products to understand variants.
- Create rules for common synonyms and misspellings (Navy Blue, Navy, Dark Blue → Blue).
- Group by vendor when many vendors use similar inconsistent labels; consider multi-select.
- Test on a staging vendor before bulk enabling rules.
- Document rules (spreadsheet) so your catalog and support teams know why values are overridden.
- Keep rules simple & focused — too many rules may be hard to maintain.
Troubleshooting
1. Rule not applied
- Verify Vendor Store Sync is active and the vendor is connected.
- Check that the option name in the rule exactly matches the vendor’s option name.
- Confirm the product has been re-synced since the rule was added (some systems require re-import or a new update to apply mapping).
2. Filters still showing old values
- Reindex or wait for the marketplace catalog indexing to refresh after mapping application.
- Ensure override values are exactly the values used in filter configuration (case and spacing).
3. Duplicate values after mapping
- If both original and overridden values appear in filters, check whether legacy products were not re-synced; run a full sync or contact support.
Limitations
- This feature maps option values only, not option types or attributes.
- If vendors change their option naming often, rules will require ongoing maintenance.
- Platform-specific constraints (Shopify, WooCommerce) may affect which option fields are available for mapping — Shipturtle will reflect platform limitations.
FAQ
Q: Can I apply one rule to multiple vendors?
A: The vendor selector supports multi-select, yes. Otherwise create the same rule for each vendor.
Q: Will this change the vendor’s product names on their own store?
A: No — mapping only affects how the product is represented on the merchant/marketplace side.
Q: What if vendor sends multiple values (e.g., Brick red / Crimson)?
A: Create rules for the common variations or normalize upstream at vendor onboarding. Multi-value parsing may not be supported automatically.
Q: Do these rules affect existing live products?
A: Typically they apply on next sync or import. Re-sync existing products to apply changes.
If you’re stuck, reach us at team@shipturtle.com or open a ticket on the Support page.