In short
There is no single review, which is why answers to this question conflict. Individual products go through an item review that Google's documentation describes as taking up to a few business days, and new accounts go through a website and policy review that can run longer while checks are made on the store. A review requested after a suspension is a separate process again and typically takes longer than either. Check the current timings in Google's own documentation, because they change.
Three reviews with three different clocks
The first is item review. Every product submitted through a feed is checked against the shopping policies and the data requirements, and items sit in a pending state until that finishes. Google's documentation has described this as taking up to a few business days, and in practice many items clear much faster, particularly on an established account.
The second is the initial account and website review. When a store first connects and claims a domain, Google verifies the site, checks that checkout works, that contact and policy information is present, and that the business appears to be what it says it is. This runs alongside item review and is the reason a brand new account can have approved-looking data and still show nothing live.
The third is a review requested after enforcement. If an account has been suspended and you request a review after fixing the cause, that is a separate queue with a longer timeline, and Google's guidance has described it as taking up to about a week. It is also a limited resource: repeated failed requests make the next one slower to resolve.
Knowing which one you are in changes what you should do, so start by reading the status in the diagnostics view rather than assuming everything is one process.
What decides where in the range you land
Account age and history matter most. An established account with a clean record and consistent data tends to see items move through quickly, while a brand new account uploading a large catalogue on day one gets the fullest version of every check.
Category matters next. Products in areas with additional policy requirements, such as supplements and health products, alcohol, cosmetics with claims, medical devices, firearms accessories, financial or subscription offers, are subject to more scrutiny and sometimes to certification requirements that must be satisfied before approval is possible.
Website readiness is the third factor and the one merchants control most directly. A store missing a returns policy, missing contact details, showing prices without tax and shipping handled correctly for the target country, or with a checkout that fails partway will hold up the account review regardless of how clean the feed is.
Data consistency is the fourth. Price and availability that differ between the feed and the landing page create mismatches, and a large number of them across a catalogue turns a routine review into a problem.
Finally, volume. A first upload of a very large catalogue takes longer to process than a staged one, which is a practical argument for launching with a subset.
What to do while it is pending, and what to avoid
Wait, and use the time on the things that will be checked. Confirm the domain claim is in place, that the policy pages are complete and reachable, that shipping and returns settings match the site, and that a test purchase can be completed on the live store.
Do not resubmit the feed repeatedly hoping to speed things up. Reprocessing the same data does not move an item forward, and on some setups a fresh upload restarts the clock for items that were nearly through.
Do not create a second account to get around a pending or suspended one. Multiple accounts for the same business are themselves a policy problem and will make the original situation harder to resolve.
Do not change the domain or move the store mid-review, since verification is tied to the property being checked.
If items are still pending well beyond the documented window, look at the diagnostics for a specific reason before contacting support. Very often what looks like a slow review is actually a disapproval with an explanation attached, or an account-level issue that is holding the whole catalogue while individual items show as fine.
Making the next one faster
Prepare the store before the first upload. Policy pages for returns, shipping, privacy and terms, written properly rather than as placeholders. A visible business name, address and contact method. Prices that display in the currency of the target country with tax handled the way that market expects. A checkout that works end to end without an account being required to see costs.
Then prepare the data. Identifiers populated, required attributes complete for your categories, availability accurate, images clean, and landing pages that match the feed at the moment they are fetched.
Launch in stages. Submit a representative subset first, confirm it is approved, then upload the rest. A small first batch surfaces systemic problems quickly and cheaply, and it means a single mistake does not produce thousands of disapprovals to unwind.
After launch, keep the account healthy so that reviews stay routine. Clear disapprovals by cause rather than one at a time, keep the feed refreshing often enough that price and stock stay current, and read the notifications rather than filtering them out. Accounts that are maintained this way rarely see the slow end of any of these timelines.
Related questions
Why are products still pending after a week?
Usually because something at the account level is unresolved rather than because item review is slow. Check whether the website claim is complete, whether there is an account-wide policy notice, and whether the products are in a category needing additional verification. If everything looks clear and the delay persists, that is the point to contact support with specific item IDs.
Does resubmitting the feed restart the review?
It causes the data to be reprocessed, which for items already in review can mean starting again rather than finishing sooner. Update the feed when the data has genuinely changed, keep to the normal fetch schedule otherwise, and let pending items complete. Repeated manual uploads are one of the most common self-inflicted delays.
Can a review be expedited?
There is no paid or priority route. What shortens the process is removing the reasons for extra scrutiny before submitting: complete policy pages, a working checkout, accurate data and a category that does not require additional certification. Where certification is required, obtaining it in advance is the only thing that moves the timeline.