Reseñas (26)
Refinar
-
Por calificación
Hasta ahora no habíamos tenido problemas con la APP, pero tras realizar un downgrade de licencia en Shopify, la APP ha dejado de funcionar correctamente indicándonos en un mensaje de error que dice:
"[{"message":"Access denied for staffMember field. Required access: `read_users` access scope. Also: The app must be a finance embedded app or installed on a Shopify Plus or Advanced store. Contact Shopify Support to enable this scope for your app.","locations":[{"line":1,"column":1188}],"extensions":{"code":"ACCESS_DENIED","documentation":"https://shopify.dev/api/usage/access-scopes","requiredAccess":"`read_users` access scope. Also: The app must be a finance embedded app or installed on a Shopify Plus or Advanced store. Contact Shopify Support to enable this scope for your app."},"path""
En ningún caso se indica en las caracteristicas de la APP que no funcionará correctamente si no es Advance o Plus.
Según Shopify, el problema lo debe solucionar MS como desarrollador, no tengo constancia todavía de que se haya hecho nada
Thank you for reporting that.
We understand the issue you are experiencing. After a Shopify plan downgrade, the connector may still reference fields that are no longer accessible on your current plan, resulting in the "Access denied for staffMember field" error.
To resolve this, please toggle the Enabled switch off and then back on in the Shopify Shop Card within Business Central. This refreshes the stored plan information and will stop the connector from requesting fields that require a higher-tier plan.
We are also working on a fix to ensure the connector automatically detects plan changes so that this manual step will no longer be necessary.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
Trash. Especially reconciliation, and even more so when dealing with orders(sales orders) where there are multiples of the same item and discount is present on one of them:
The item gets broken down into two item lines, and when you sync the shipment back to Shopify, the connector doesn’t know what to do with two or more of the same item on different item lines.
Thank you for your feedback. We understand the frustration with how discounted and non-discounted lines for the same item are handled during shipment synchronization back to Shopify.
We are really happy to share that we found a way to solve this problem and released a fix as part of the 2026 release wave 1 update, which is already available. We encourage you to upgrade to the latest version of Business Central to benefit from it.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
Really good integration, there are some limitations, but for a free addon I feel it's very stable.
There are alot of quality of life things that make it easier, but there are some downsides, like BOM handling and syncing lead times (for out of stock items) doesn't work out-of-the-box.
Thank you for your kind words and for using the Shopify Connector! We are glad to hear that the integration has been stable for you.
We appreciate the feedback on BOM handling and lead time synchronization. If you would like to see these capabilities added, we encourage you to submit your suggestions at https://aka.ms/BCIdeas. This helps us prioritize future improvements based on customer demand.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
Directamente no funciona, aunque te dice que si, que esta todo "completado", tipico Microslop
Thank you for trying the Shopify Connector for Business Central. We are sorry to hear that your experience has not been as expected.
We recommend reaching out to your Microsoft partner who can help review the configuration and resolve synchronization issues. If you have suggestions for improving the product, we would love to hear them at https://aka.ms/BCIdeas.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
We have been using the system without any issues for a few months, but after the recent product synchronization, Business Central is no longer mapping the products correctly.
We are still receiving orders; however, they come through without SKUs—only product titles. As a result, sales orders are not being created automatically.
What’s more, the system is not showing any errors in the log entries, even though some products are not mapped and others are not synchronized at all.
At this point, we’ve reached a dead end and had to manually map all 600 SKUs, which is extremely time-consuming and frustrating.
Thank you for taking the time to share this feedback.
We are sorry to hear about the product mapping issue. We recommend reaching out to your Microsoft partner so they can review your Shopify Shop Card configuration and sync log entries to help identify why SKUs are no longer mapping correctly after the product synchronization.
If you have suggestions for improving error visibility in these scenarios, please share them at https://aka.ms/BCIdeas.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
Segunda vez que en Business Central me indica que el concetro debe ser actualizado en Shopify y no existe ninguna opcion para actualizar. Cada vez que se actualice debere desinstalar la aplicacion y volver a instalarla?
Thank you for reporting that.
Shopify releases a new API version every three months at the beginning of the quarter, and supports each version for 12 months. The updated versions might contain important changes, so it's important to uptake Shopify API versions in major releases of Business Central. Typically, new versions of APIs increase stability and security, and enable additional capabilities.
It means that The Shopify connector released in 2024 release wave 2 (October 2024) relies on API 2024-07, which is supported until July 1, 2025. To continue to use your integration, you will need upgrade to the latest version of Business Central before this date. For example, the Shopify connector released in 2025 release wave 1 (April 2050) uses the Shopify API that was released in January 2025 and can be used till January 2026.
To upgrade connector you also need to upgrade Business Central. We are exploring option how to align Shopify, Business Central the Shopify Connector release cycles to reduce impact on your operations.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
It will be a nice connector. For the moment, whenever we synchronize an order with fulfilled status (both online and POS) the "location_id" in the Shopify order is wrong. We have to use an extra API call to "fulfillment_orders" method to get the correct location_id.
We appreciate your input, and we are glad to hear that you found a solution for your issue.
As your feedback sounds very similar to support case you submitted, we are not sure if you received our reply. Let us duplicate some of information here as it might impact your solution.
Be aware that the Location in the header field is being deprecated and replaced by information from Fulfillment Orders. See documentation to Shopify APIs: https://shopify.dev/docs/api/admin-graphql/2024-01/objects/Order#field-location.
Connector works exactly as recommended and uses information for Fulfillment Orders.
In cases when fulfillment happened on Shopify closed fulfilment orders are not imported, which in some cases (think of POS scenarios with multiples stores) led to undesired behaviour. The adjustment of connector will be available with next minor updated (24.4).
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
I love it! but when I sync a new product, all tags are removed from many of my products. I would like to know how to synchronize the products without deleting the labels or supplier names, please!
Also if it could be synchronized faster, products that were already marked as "sold out" tend to be sold.
Thank you for taking the time to leave a review. We're glad you enjoyed the connector to Business Central.
We would like to let you know that we found the reason tags were removed. It appears to be a specific scenario where part of product master data is managed in Business Central, while tags are assigned in Shopify. We adjusted connector so it won't include tags section if they are not defined on Business Central. That should address your scenarios. The fix will become available with one of the upcoming minor updates.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
When we enter the Shop URL in Business Central and click Enable, the system starts the OAuth authorization process but gets stuck on “Waiting for a response – do not close this page.” After some time, we receive the error “No Access token for the store. Please request an access token for this store.”
This issue occurs even when the Shopify Store Owner attempts the connection. We have already checked browser settings, pop-ups, cookies, and tried different browsers and incognito mode, but the OAuth authorization still does not complete.
We would like assistance in resolving the OAuth authentication issue so that the Shopify store can successfully generate the access token and be enabled in Business Central.
Thank you for reaching out,
The symptoms you are observing are usually related to an incorrect Shopify Admin URL. Recently, we have noticed this occurring with trial stores after merchants configure a new URL. To address this, we are rolling out an enhancement that will detect the use of redirect URLs and provide better guidance. In the meantime, please try the workaround provided below.
The trial stores (in the past we saw similar behavior with Shopify Plus Sandboxes) are pre-provisioned by Shopify with some interim URL, like xxxxxx-xx.myshopify.com (where x is any letter or number), the fact that store gets new URL later doesn't change the fact that inside it is still considered as xxxxxx-xx.
The biggest challenge is to figure out the url to use in the Shopify Connector. I suggest to open Shopify Admin, navigate to Setting and then to Domains. You will see all domains associated with your store. If you see something like xxxxxx-xx.myshopify.com - it worth trying it out.
As a side note, do you work with a Microsoft partner? They are a valuable resource and can assist at different stages of implementation. If there is a problem that the partner cannot resolve, they can submit a support request to Microsoft.
Kind regards,
Business Central Development Team
Está muy lejos de adaptarse a la realidad de la operativa del POS. Tiene muchas limitaciones y no es recomendable su instalación.
We appreciate your feedback and rating of the application!
For more information on how the connector handles order editing, please refer to this article:
https://learn.microsoft.com/dynamics365/business-central/shopify/synchronize-orders#impact-of-order-editing .
We recently discovered a scenario that involves return/exchange performed via POS, where Shopify creates two refunds. We have fix pending deployment that will ensure both refunds are properly processed.
Kind regards,
Microsoft Dynamics 365 Business Central engineering team
