Notice27
DocumentationAccountStart free trial

Real WooCommerce · safe fictional state

Choose a product. See why Notice27 responds.

The live demo uses a pinned WordPress and WooCommerce stack with Notice27 2.0. Switch between Shopper and Inspector views, change language, load a scenario into the cart and follow it through checkout, order, email and account previews.

Six guided scenarios

From an ordinary good to a mixed-cart decision.

Every example identifies what the merchant confirmed, what Notice27 can show and what still needs review.

02

Stainless Steel Kettle

GARAN record

Ready after merchant-confirmed guarantee facts
Open scenario →
05

Wireless Keyboard

Good with digital elements

Updates reviewed separately
Open scenario →

Current customer-facing evidence

See the complete storefront context before opening the store.

These are full, current captures from the isolated demo—not a mock-up. Select either image for the original resolution or follow its live journey.

Current Notice27 demo product page showing the complete notice below Add to basket
Product page · customer notice below Add to basket · current Notice27 2.0 demo environment
Current Notice27 demo mixed cart showing the customer notice below the cart lines
Mixed cart · reviewed line-by-line state · Inspector selected for explanation

Two views

Shopper output stays simple. Inspector detail stays available.

Shopper

Only the customer-facing notice, relevant guarantee/update information and supported order output. No raw reason codes.

Inspector

A human explanation of result, market, language, product or variation, general notice, GARAN, digital/update facts, blockers and placement. Raw codes stay collapsed under Technical details.

Implementation boundary

Notice27 is implementation software, not legal advice, certification, EU endorsement or a guarantee of compliance. Applicability depends on product, buyer, transaction, target market, language and national law. The demo does not qualify GARAN or imply broad digital-content or digital-service coverage.

Review the pinned runtime and evidence boundaries →