Has anyone implemented the required shipment and cancellation feeds to submit to Google as required to be a "Google Trusted Store"?. It seems like it might be an enticement to potential customers online. I know all the info is in the DB but have no idea how to pull it out.

The Google requirements can be found here  http://goo.gl/kyh2V" rel="nofollow - http://goo.gl/kyh2V

Thanks

Alan

I'm interested in any feedback on this. I could easily be temped to start working on a solution if there is sufficient demand. Couldn't break ice on it until Q2 2013, though at this point.

If you are interested, we're actually pressing our beta of this right now. Should have this launched on a live store in the next couple of days.

There are several things required to do this that don't exist in the PC database and some challenge with building the value of gts-o-discounts (as the data for this is rather disparate in PC). 

There are also some challenges to overcome to make this generic for all users, such as setting "padding" for estimated ship date and estimated delivery date (very important that these are 90% or better accurate) -- for example handling these dates on a Friday if the merchant doesn't process orders over the weekend.

The biggest challenge here for making it generic, though, is parsing the value for the shipping carrier. Lots of thorny issues here, but not too bad if tailored for a specific merchant's needs at this point in our beta.

To make this a generic extension, we still have two challenges:

1) Factoring the estimated ship and (optional) delivery dates when a weekend is in the mix (say an order is received on a Thursday; the merchant typically takes 2 days to process and ship. A flat date + 2 days would land that on a Saturday and maybe they don't process orders over the weekend. Should that go to date + 2 + 3? What if they take only 1 day, or maybe 3 days?). We just needs more real merchant scenarios to refine how to calculate this. The estimated ship date is crucial, though, as this is what Google calculates the score upon -- and it must be 90%+ accurate.

2) Determining the value for the carrier. This is a big challenge as there really isn't good data in PC's db to determine this, esp. as a merchant could use any carrier despite what the customer selected when checking out. Or, the checkout shipping options could be offline and then merchant decides what carrier to use. The only real solid bit of data to go on is the tracking number supplied (and if that's not supplied, then what?) as the carriers we've looked at so far (USPS and UPS) appear to prefix a merchant identifier in their tracking numbers. We'll need more real world examples to come up with a generic routine for this.

If you are interested in beta testing our solution with these two caveats in mind, please PM me.

BTW, the order threshold level for GTS is now 200 orders/28 day rolling cycle.