Amazon orders Not Syncing correctly since August 7th

​@greggchopper ,

Which connector are you on, the native Amazon one or a third party? And are these seller-fulfilled or FBA? On the native connector those are two different entities, Sales Order and Marketplace-Fulfilled Order, and they break for different reasons.

Worth spelling out what "not correctly" looks like too: nothing coming in at all, orders arriving with fields wrong or missing, or records sitting unprocessed. Sync History (BC301000) for that entity from August 7 forward will tell you which, and it carries the error text on anything that failed.

Post that and another seller can tell you fast whether they're seeing the same thing.

Using native Amazon Connector and these are seller fulfilled and marketplace orders, some not coming over at all, and others coming over hours and days later. We have two stores and seeing orders coming over labeled for the wrong store and the order for the right store never coming over. Started on August 7th and Acumatica hinted at an API change but no solution insight and it is impacting our Amazon store of being at risk now since we cannot acurately update inventory.

To confrim they are not coming over into the sync history period so no way of knowing what the error is if any like normal orders that may error

​@greggchopper ,

Before writing off Sync History (BC301000), two things about that screen. The Store box defaults to whichever store has the Default check box selected, so with two stores you're seeing one of them unless you switch it. And the Filter List holds more than the obvious tabs: Aborted, Deleted, Failed, Filtered, Inactive, Invalid, Skipped, plus All Records. Aborted is the one people miss. A record lands there once it fails more times than the entity's Max. Failed Attempts allows. Check All Records against each store before concluding the orders never arrived.

If they're genuinely not there under either store, incremental prepare may not bring them in, since incremental only takes records modified since the last successful preparation. Prepare Data (BC501000) in Full mode with a date range from August 7 pulls everything created or modified in that range whether or not it's been processed before. Incremental by Date is the narrower one, records modified in the range that haven't been processed yet.

Also worth a look with two stores: Amazon Stores shows a maximum number of stores allowed by your license. Past that limit, only the stores within it sync, and they're picked alphabetically.

No idea what changed on the 7th. I'd want to know that too.

I am aware of all of this and the orders are not coming over at all period. I did a full prepare and within a specific date range and I still did not get all orders and reality was it created more mess as despite the date range I was getting duplicate old orders, orders labeled to the wrong store and orders outside of the date range. 

Our license accounts for the two stores so that should not be the issue, now on our third Acumatica engineer in 3 weeks trying to resolve this. If we lose our SFP status this will be catastrophic in terms of lost revenue and we will likely take legal action.

Experiencing the same. 

@Jeff96 - sorry you are experiencing this as well but I am glad to hear it is just not us

We’re live with the connector for two months now. And the experience isn’t good.

We have been using it for two years and the last 2-3 months have been painful, mostly on Product Availability Sync and now the Sales Orders. Feedback from many VARs and developers is if your a serious Amazon retailer do not use the connector use a 3rd party like Celigo or Pipe17 or build a custom one. The system just cannot handle volume and Acumatica staff seemed to be disconnected on how Amazon Seller Central really works. Buy Shipping from Amazon as an example, to get OTDR from Amazon and be protected there is no way in Acumatica to do this.