1. Overview
With WeSupply, you can configure estimated delivery dates (EDD) based on product attributes such as color, size, or vendor. This ensures customers receive accurate delivery estimates for different types of products, improving transparency and the overall shopping experience on your Magento store.
Note: If you want to display the same promise delivery date for all products regardless of attributes, you can leave the Conditions section empty and only configure processing time if needed.
2. Pre-requisites
Before setting up product attribute–based rules, make sure:
- Your desired product attributes are configured in Magento (e.g., color, vendor, size).
- These attributes are exported to WeSupply.
- Go to Magento Admin → WeSupply Extension → Configuration → Advanced Settings → Product Attributes To Be Exported For Return Logics.
- Select the attributes you want to use, then click Save Config.
- From now on, those attributes will sync to WeSupply each time a new order is imported.
3. Step-by-Step Instructions
Step 1 – Identify the Product Attributes
- Make sure you have the right product attributes exported to WeSupply by going to your Magento Admin Panel → WeSupply extension → Configuration → Advanced Settings → Product Attributes To Be Exported For Return Logics.
- Select the desired product attributes and click Save Config. From now on, these product attributes will sync to WeSupply each time a new order is imported.
Step 2 – Create a New Estimation Rule
- Log in to your WeSupply Labs account and navigate to Settings → Delivery Promise Date → Promise Date Policies.
- Click on the Add Logic button to create a new estimation rule based on a product attribute.
Step 3 – Define Rule Conditions
- In the Conditions section, choose the product attribute you want to base the rule on.
- Example: Select Product Attribute from the dropdown.
- Enter the details:
- Attribute Name: Use the Magento attribute code (lowercase, e.g., color).
- Value: The attribute value (e.g., red).
- Condition: Equals, does not equal, contains, etc.
- Click Add.
Example: Create a rule for all products with color = red.
Step 4 – Add Additional Processing Time
- In the Estimate Window section, enter the number of days to add to the processing time.
- Example: Add +3 days for red-colored products.
- This ensures delivery dates reflect the extra time needed for processing.
to create a new estimation rule based on a product attribute.
Step 5 – Save the Rule
Click Save Changes to apply your new estimation rule.
Step 6 – Add More Rules (Optional)
Repeat Steps 2–5 to create additional rules for other attributes (e.g., size, vendor, or backorder items).
Step 7 – Test Your Rules
- Add products with different attributes to your cart.
- Verify that the estimated delivery date updates according to the rules you’ve configured.
- For a quick check, you can also use the Delivery Promise Date Simulator in WeSupply.
4. Examples / Best Practices
- Backordered products: Add 14 days for items marked as “backorder.”
- Custom products: Apply extra processing time for engraved or personalized items.
- Seasonal delays: Create attribute-based rules for products with longer lead times during peak seasons.
- Always double-check the Magento attribute code is spelled correctly in lowercase (e.g., color, not Color).
5. Troubleshooting / FAQ
Q: My rule isn’t applying to products. What should I check?
- Confirm the attribute is correctly exported to WeSupply.
- Verify the attribute name and value match Magento exactly.
Q: Can I have multiple rules for the same attribute?
- Yes, but make sure they don’t conflict. For conflicting cases, you may need to use Exclusive Logic (see our article on Exclusive Rules).
Q: Do these rules override the default delivery promise date?
- Yes. If a product matches a rule, the estimate will include the additional processing days. If no rule matches, the default delivery estimate applies.
✨ With Estimated Delivery Rules based on product attributes, you can provide customers with precise, reliable delivery expectations that match the reality of your operations.
Comments
0 comments
Article is closed for comments.