Amazon sellers · Status at source date: Update
Estimated FBA receiving times, a Vendor Central "Canvas" beta and the Business Reports retirement banner
Three Seller and Vendor Central observations this week; none has an Amazon page we could open.

What changed
For you, this means inventory timing and reporting are both changing in the console, so check the Manage Shipments page before your last pre-peak inbound.
- Estimated receiving times for US FBA shipments, by fulfilment-centre destination, rolling out on Manage Shipments over the coming weeks; estimates show when most units will be received and vary by season. 🥇 First contributor: Mila Dubykivska, 12 November. - A "Canvas" AI assistant in Vendor Central, in beta for selected accounts, answering plain-English questions about catalogue content, availability, Net PPM and traffic with charts; Canvas launched in Seller Central in March. 🥇 First contributor: Martin Heubel, 9 November. - Business Reports retiring by year-end in favour of Custom Analytics, a banner first reported in October; Mansour Norouzi compares the two and finds the data identical and the new layout rougher. Reminder.
These observations belong to different operational workflows. Estimated FBA receiving times concern inventory planning, Canvas concerns a Vendor Central interface, and the Business Reports banner concerns reporting continuity. Assigning all three to the advertising team alone would leave important dependencies unresolved.
For receiving estimates, compare the displayed timing with the shipment and stockout risk being managed. An estimate should not be treated as a guaranteed receiving date. Keep the logistics owner involved when deciding whether a promotion or advertising increase can be supported by available inventory.
For Canvas, inspect the beta's actual account scope and available functions before promising a new workflow to the wider team. A screenshot establishes the interface seen by the contributor, not universal vendor access. Document the account and purpose of any test.
For the reporting banner, identify the affected reports, exports and downstream dashboards. Preserve the data and definitions needed for continuity, and confirm the replacement route before the stated retirement. A banner announcing a future change does not prove that every report has already stopped working. Keep dates and access conditions attached to the individual item rather than combining them into one general platform deadline.
Sources & contributor credit
- Original sourceLinkedIn ; Mila Dubykivska
- Supporting sourceLinkedIn ; Martin Heubel
- Supporting sourceLinkedIn ; Mansour Norouzi
- Supporting sourceAbout Amazon ; Canvas (March)
Original creator unverified
Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.







