Many products are subject to restrictions in certain jurisdictions. For example, live plants, live animals, alcohol and firearms often have rules around where they can be shipped. If this applies to your Zen Cart based shopping cart, take a look at my Zen Cart Shipping Restrictions page.
You want to sell your wares in Google Shopping? Great! By all means, build a feed from Zen Cart for Google Merchant and get started. But remember the rules: Google wants you to list shipping costs along with your products for every region you advertise in.
Here are the most common ways to do this:
Simple to configure and maintain
Simple to configure and maintain
Carrier rate (UPS, USPS, Fedex)
Rates are automatically calculated based on carrier rates for all users (not negotiated rates). Only available in some countries (USA, AUS). You may add a surcharge (% or fixed amount).
Percentage of order total
Simple to configure and maintain and allows for varied shipping rates based on price
Unique shipping costs for one particular product
Specify the shipping price within the feed using the shipping attribute.
Allows you to manually override account settings for a product with unique shipping rates
Google maintains a team of auditors who will compare what’s in the feed to what is shown on your website in the Shipping Estimator, and complain about any variance between the two. Now according to their own rules, you are allowed to “overestimate” the shipping cost in the feed (see rule below), but even then, I have received complaints from them. Per Google,
“To show ads to a particular country or region, you must offer shipping and correctly set up shipping costs for that area. The shipping costs that you submit to Merchant Center must match the costs you charge on your website or at least overestimate those costs.”
In other words, it’s ok for the feed to show a higher shipping cost than your website. It’s not ok for your website to show a higher shipping cost than the feed.
If you determine shipping costs algorithmically using your own logic, you’re going to have to figure out some way of mapping this to one of the techniques in the table above for the purposes of the Google feed. Again, per Google,
“Keep in mind that if you dynamically choose where to ship from at the time the user checks out, there is currently no way that this can be configured in Google Shopping.”
You quote negotiated rates (for example, using the Zen Cart upsxml shipping module). If you use Carrier Rates in Google Shopping, they will retrieve non-negotiated rates; this will cause the rate shown in Google Shopping to be higher than what is on your website. Although this is permitted according to their rules, you may have to argue with them about this.
You have enabled multiple shipping modules, or multiple services within a carrier. In this case, you may be forced to show all relevant rates, not just the lowest or most common one.
Many moons ago, the “next” version of Zen Cart was given the name 1.6.0. As time moved on and features were added to the code for this release, it became clear that it was going to be different enough from the 1.5.x branch of Zen Cart that a bump in the major number made sense. So the release name was changed to 2.0. But many other things still used the old name – which was kind of confusing.
I have added an optional feature to Zen Cart 360 Sales Reporting (link) which shows recent direct deposits on the admin dashboard. Update admin/index_dashboard.php, and at the end of the file, add this block of code:
Zen Cart Coupon Single User has been upgraded so that you can now restrict a coupon to any email address on a single domain, not just a single email.
So for example, if you want to permit a coupon to only be used by customers with a “@BigClient.com” email address, you would create a coupon code starting with “@BigClient.com”, such as “@BigClient.com_save_ten” or “@BigClient.com-half-off”.
There’s a bug in Zen Cart 1.5.5 that causes the State dropdown not to be correctly populated when you set Configuration->Customer Details->State - Always display as pulldownto true in Admin->Configuration->Customer Details. It causes your State dropdown menu to look like this:
even though the value of State has been set.