FieldStack Webstore Version 11.4

Modified on Mon, 4 Nov at 2:41 PM

New Feature: Ship to Store

Preorder Ship to Store 

If an item has a future release date and is not marked as unavailable, In Store Pickup can be allowed based on a setting.





 Action Required:

A back-end setting controls BOPIS for pre-order items. If you would like this enabled on your webstore, please contact FieldStack.
Allow PreOrder BOPIS - Allows placing of pre-order BOPIS.




Other New Features

Ability to disable shipping references 

FieldStack webstores are now equipped to have shipping disabled. If you want to offer Local Delivery/Same Day Delivery and Curbside/BOPIS, but would prefer not to be integrated with any shipping partners, the availability statements and visuals for shipping can be turned off.


 Action Required:

If you would like to disable shipping, FieldStack can help with back-end settings.

Text strings on the site would need to be evaluated and updated (example: “Shipping Addresses” “Free Shipping over $x.xx” etc.) HTML blocks that refer to shipping would also need to be edited and updated.

Any existing autoship customers would need to be contacted and those orders cancelled or reordered using another fulfillment method.




Improvements

  • Allow curbside text even when an item is out of stock - Historically, if an item was not available for Curbside/BOPIS, it would show the store address but not the specific fulfillment method. The Curbside Pick-Up text (or equivalent) will now show before the address regardless of availability.

  • Contest Page Updates - Contest Page entry forms have been updated with better spacing and non-internal captcha added for validation.
  • Contact Us / Need Help? link improvements - The Contact Us form will create an email that sends a customer notification to your customer service inbox from your internal email. This can be blocked by some email hosting platforms and is limited in its usability.
    Two new possibilities are being offered:

    1. The ability to swap the contact Us form with custom script that would come from a customer service system like ZenDesk.
    2. The ability to turn off the Contact Us form from the Order History page.

     Action Required: 
    If either of these solutions is wanted, please contact FieldStack for assistance.




Bug Fixes


  • Pickup person/phone could be blank if customer clicked buy button quickly enough – Pickup person and phone number may be required for Curbside/BOPIS. If a customer changed their order from shipping to BOPIS and tapped the Place Order button quickly, these necessary fields could be previously bypassed. 
  • Preowned items could be added in duplicate from wishlist/saved for later – From a Saved for Later list, double-clicking Buy Preowned would add 2 copies of an item to the cart. This has been fixed.
  • Local Delivery Address Checker didn’t update saved addresses eligibility – When checking address against local delivery, Check My address would show eligibility. If a new saved address was selected, the Eligibility would not refresh. This has been updated.
  • Auto apply coupons could be manually added a second time – If a customer knew the promo code for an auto apply coupon, they could manually add that code to the cart a second time, doubling the discount. This has been prevented.
  • Bogo Promo with no get items will discount any item in online cart – If a BOGO program was set up with buy items but no get items, satisfying the buy portion would apply the get offer to the next item in the cart. This has been prevented by not allowing BOGO coupons to be created that have no get items.
  • Adding Specialty Tax item(s) to a cart first would apply that same tax to other items – If a customer added a Specialty Tax item to their cart, followed by other items, the items added after the Specialty Tax item(s) would carry the same tax rule as the special item. Going forward only the Specialty Tax item will be affected.



 





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article