Preline Upgrade - Ecommerce

Problem Statement

As a publisher admin, I experience an inconsistent dashboard experience because the Ecommerce Orders, Products, and Product SKU pages still run on the legacy Bootstrap-era UI while most of the rest of the dashboard has already moved to Preline, which results in jarring context-switches and duplicated maintenance effort across two design systems.

User Story

As a publisher admin, I want the Ecommerce Orders, Products, and Product SKU pages rebuilt on Preline, so that I get the same modern, consistent experience I already have on Customers, Subscriptions, and Invoices.

Definition of Done

A feature is done when:

• Given a publisher views the Orders, Products, or Product SKU index/create/edit/show pages, when the page loads, then it renders on the Preline layout with full feature parity to the current legacy pages.

• This change will impact the UI only (Ecommerce\OrderController, Ecommerce\ProductController, Ecommerce\ProductSkuController and their Blade views); no API, SDK, or Integration changes expected.

• This solution will include the following limitations: legacy views may need to stay reachable via a ?legacy=1 fallback during rollout (same pattern already used for Addresses/Fulfillments); full filter/search parity may require a follow-up pass.