In case Cloudflare’s DNS servers stop working properly, we can switch the DNS servers to GoDaddy’s DNS and upload all the records from a file.
For it we need make some changes in domain control panel on GoDaddy side:

1. Login to GoDaddy, click to My Products

   

2. Find domain saclab.com and click DNS

   

3. Under Nameservers, click Change Nameservers

   

4. Before change Nameservers save current nameservers, current nameservers Name Server: ADRIAN.NS.CLOUDFLARE.COM and YOXALL.NS.CLOUDFLARE.COM, we will use thethes, when will back to the CludFlare DNS, after that Choose: GoDaddy Nameservers and press Save

5. From this moment, we are using GoDaddy DNS servers (nsXX.domaincontrol.com, nsYY.domaincontrol.com).
   To configure our domain records on these DNS servers, we need to go to DNS Records – Actions – Import Zone File (the zone file can be downloaded at the bottom of this page).

   

6. After that we a ready to upload file with domain records:

   

7. Choose the file and upload:

   

8. When file uploaded press Apply Zone File

   

   From this moment we a configured our domain on GoDaddy DNS servers and upload dns records. When CloudFlare recovery the services we should back DNS to the CloudFlare. For it we should back the setting with we changed on Step 4

9. Change back to the CloudFlare DNS:

   

DNS configuration Files:

saclab.com_2025-11-18.txt

Useful links:
Check status of cloudflare – https://www.cloudflarestatus.com/

General info

Implementing the "Featured" logic into slider widgets for the Homepage and Product Detail Pages (PDP).

User story

I want specific sliders for featured items

So that I can increase conversion on high-priority bags (Manually Starred/Price Drops/Trending) without manual curation every day.

Acceptance criteria

ID	Scenario (Gherkin)	Screenshots / Wireframes
01	Scenario: Homepage Featured Slider Given The Homepage loads When Rendering the "Featured" slider (between New In-Slider and “Shop by Brand” section) Heading “Featured” CTA “SHOP ALL” links to /shop with “featured” sort Then Fetch items where Starred = True And Filter strictly by Stock Status = In Stock And Order by Key B (_featured_sort_index) And Do NOT apply Model Flip logic. And link existing “New in” CTA to /shop with “new in” sort
02	Scenario: PDP Featured Slider (Context Aware) Given User is viewing a specific product (e.g., Hermès Kelly) When Rendering the bottom slider (Replacing "You may also like") Then Prioritize Starred items from the Same Brand (Hermès) And If fewer than 4 items found, fill with Global Starred items And Order by Key B (_featured_sort_index) And link “browse all [Brand] to brand page sorted by “Featured”.

General info

This story covers how the two lists from Story 1 are rendered to the customer, how the "Model Image" flip works, and the mobile sort interaction.

User story

As a Customer

I want to see the best "Featured" items by default, but easily switch to a chronological "New In" view

So that I can browse curated picks or see the latest drops exactly as the stylists arranged them.

Acceptance criteria

ID	Scenario (Gherkin)	Screenshots / Wireframes
01	Scenario: Default "Featured" View Rendering Given The user lands on /shop/ (No filters active) When The page loads Then Render Block 1: All Starred★ items, sorted by Key B (_featured_sort_index) And Render Block 2: All remaining In-Stock items, sorted by Key A (menu_order) And The result shows “Starred” first, followed immediately by the color-sorted catalog (sorted manually by salsteam).
02	Scenario: Switching to "New In" View Given The user selects "Sort: New In" When The grid reloads Then Render ALL items (Stock + Preview) sorted strictly by Key A (menu_order) And Ignore Starred★ status (Starred are treated as normal items) And Disable the Model Image Flip logic completely.
03	Scenario: Model Image Logic (The 1-in-5 Rule) Given The user is on the Featured View (no Brand/Color filters active) When The grid renders Then Check slots 2, 9, 16, 23, 30… (Every 7th item, offset by 2) And IF the product in that slot is Starred AND has an image ending in _1M[.jpg or other file type] Then Show Model image as Main, Packshot as Hover Else Show Standard Packshot as Main.	Visual Proof (How it lands) On 5-Column Grid: #2: Row 1, Col 2 #9: Row 2, Col 4 (Nice jump to right) #16: Row 4, Col 1 (Nice jump to left) #23: Row 5, Col 3 (Center) Result: Perfectly scattered. On 4-Column Grid: #2: Row 1, Col 2 #9: Row 3, Col 1 #16: Row 4, Col 4 Result: Wide scatter. On 2-Column Mobile: #2: Right side #9: Left side #16: Right side Result: Balanced.
04	Scenario: Sort Interaction Given The user is on Mobile or Desktop When They view the top right header (Action Bar) Then The Sort Label displays the active text: "Sort by Featured ⌄" or "Sort by New In ⌄" And Clicking the text opens the standard sort drawer with order Featured>New In>Price low to high>Price high to low.

General info

We are introducing two sorting "Keys" (indexes) in the database so the Sales team can manage the "New In" color gradient independently from the "Featured" VIP list.

• Key A (menu_order): Controls the global "New In" sort.

• Key B (_featured_sort_index): Controls the sort of Starred items only.

User story

As a Merchandiser

I want to sort my "New In" items by color without being disrupted by "Price Drop" items (and vice versa)

So that I can maintain a perfect aesthetic feed while still highlighting important VIP bags in a separate view.

Acceptance criteria

ID	Scenario (Gherkin)	Screenshots / Wireframes
01	Scenario: Sorting in "New In" Workspace Given The Admin is in the Product List And The filter "New In / All" is selected When The Admin drags and drops an item (e.g. a new upload) Then The system updates the standard menu_order (Key A) And This change does NOT affect the order inside the "Featured/Starred" view (Key B) And If a new product is created OR comes back in stock, it automatically moves to position #0 (Top). And Admin can “Star” ★ a bag to add it to the “Featured” Workspace
02	Scenario: Sorting in "Featured" Workspace Given The Admin is in the Product List And The filter "Starred★ Only" is selected When The Admin drags and drops a Starred item Then The system updates the _featured_sort_index (Key B) And This change does NOT alter the menu_order (Key A) used for the “New In” sort.
03	Scenario: Pending Boost Queue Given A product triggers "Price Drop", "Trending", or "Back in Stock" When The event occurs Then The item is added to a "Pending Boost" counter/list And It is NOT automatically moved to the top of the frontend Featured view yet And The Admin must click "Approve/Star★" to officially push it to the top of Key B. And The Admin has an option to bulk edit “Add/Remove ★”

General info

We are decoupling the "New In" view from the "Featured" view to allow independent sorting.

• New In: A strictly chronological (but manually color-sorted) view.

• Featured: A curated view showing Starred VIP items (Price Drops, Trending) at the top, followed by the New In list.

Epic ticket:

User stories

Visual design

Desktop:

Mobile:

Issues in this release

Before you share the page, review the contents of each Jira issue and remove any sensitive data.

Issue	Summary	Issue Type
SCLB-1706	Bag accepted = "yes" function does not work in Airtable	Bug
SCLB-1699	Automatic email confirmation	Task
SCLB-1698	[BUG] SYB step 4 review -> back button leads back to log in window	Bug
SCLB-1688	Fix search bar stability	Task
SCLB-1686	Full-set feature:	Task

Summary

New Features

Improvements to existing features

Bug fixes

Overview

The purpose of this page is to prepare a technical Risk & Mitigation Plan for the upcoming Black Friday campaign.

This plan will help ensure that the website remains stable, secure, and performant under increased traffic and system load.

Each identified risk should include a short description, likelihood, potential impact, and a proposed mitigation strategy.

The engineering team will review this plan and confirm the necessary actions before the campaign begins.

Risk & Mitigation Plan Table

On-Call Availability During Black Friday

During all three days of the Black Friday campaign, our team will remain fully on-call to react immediately to any issues, performance drops, or unexpected load spikes.

The following team members will actively monitor the system:

• DevOps – server performance, infrastructure health, Cloudflare.

• Developer – application behaviour, checkout flow, logs.

Throughout the campaign, we will continuously observe:

• Server load and resource usage

• Cloudflare traffic and potential security threats

• Error logs and 500-error spikes

• Checkout and payments stability

Our goal is to ensure maximum uptime, performance, and stability during the entire Black Friday period.

Issues in this release

Before you share the page, review the contents of each Jira issue and remove any sensitive data.

Issue	Summary	Issue Type
SCLB-1676	SYB submission don’t get through if the internet connection was lost on the first step	Bug
SCLB-1663	Story 30.1 Filter Logic for Model Visibility	Task
SCLB-1658	Story 29.5. Banner System & Countdown Logic	Task
SCLB-1657	Story 29.4. Scarcity Signals	Task
SCLB-1656	Story 29.3. Drop Logic & Product Selection	Task
SCLB-1655	Story 29.2. Live Drop System & Private Links	Task

Summary

New Features

Improvements to existing features

Bug fixes

Issues in this release

Before you share the page, review the contents of each Jira issue and remove any sensitive data.

Issue	Summary	Issue Type
SCLB-1674	Failed payment page – text of the button isn’t visible	Bug
SCLB-1666	Story 43.2 Send bag First Time Seller adaptation: AC4 stopped working: Seller outside of Germany not pre selected to 9AM – 5PM	Bug
SCLB-1633	Replace custom “Continue with Google” and “Continue with Apple” buttons with official branded versions	Task
SCLB-1565	Story 28.5 Story: Exotic-Leather Checkout Flow – EU Shipping Pop-Up & Streamlined Address Handling	Task

Summary

New Features

Improvements to existing features

Bug fixes

General Info

We introduce a new Featured system to highlight high‑value or time‑sensitive bags across the site.

What’s included

• Homepage Featured slider (new), matching the New In slider’s design and placed directly below it.

• Product Feed default sort = Featured → New In with infinite scroll.

• PDP Featured slider (new) replaces “You may also like”; shows items from the same brand.

• A simple, single control: WooCommerce ★ Featured star.

• Automation that links Scarcity Signals and inventory events to the ★ star and gives a rank boost so items appear near the top without manual work:

  • Price Drop (7 days)

  • Trending (14 days; tag is added manually in Airtable)

  • Back in stock (7 days; returns, re‑published inventory, dropship re‑enabled)

Rules we keep

• Sliders show in‑stock only.

• Sold‑out items stay starred if applicable, excluded from sliders, and appear at the bottom of the Featured feed with a “Sold out” label.

• No model‑photo changes for now (standard packshot cards).

• Filters and search (brand, model, etc.) work exactly the same in the new Featured view.

User Story

As a customer, I see a curated, high‑impact “Featured” selection (discounted, trending, or newly available again) so I can quickly browse the most relevant pieces.

Design

• Homepage Featured slider: same look/behavior as New In, placed directly beneath it; ordered by Featured rank.

• Product Feed: default = Featured first (ordered by manual drag‑and‑drop rank); when no more ★ items, the feed continues seamlessly with New In (infinite scroll).

• PDP Featured slider: brand‑limited (Hermès, Chanel, Bottega Veneta, Dior); excludes sold‑out; same card design as grid.

• Sold‑out section (feed): sticky footer section of the Featured feed listing sold‑out Featured items with a label; not shown in sliders.

Acceptance Criteria

Team Workflow (non‑technical)

• After each drop, the Sales Team stars featured bags and does light ordering via Products → Sorting (drag‑and‑drop).

• Weekly / twice‑weekly housekeeping: remove ★ from outdated items and from long‑sold‑out items (if desired).

• No extra steps needed to surface Price Drop, Trending, or Back‑in‑Stock items—the automation stars and rank‑boosts them for a short window so they naturally rise to the top even if the page hasn’t been manually re‑sorted yet.

Notes (for devs)

• We reuse Woo’s native Featured ★ and menu_order.

• Auto rank boost = move the item near the top of Featured by adjusting menu_order (e.g., lower than current minimum). No automatic “rank restore” required; editorial re‑ordering can override at any time.

• Unstarring happens only for stars created by automation after the 7/14‑day windows end; manual stars remain.

• No new badges for Back‑in‑Stock; this is a surfacing rule only.

• Sliders always query in‑stock; the feed shows sold‑out at the bottom.

• Same query semantics mean filters and search behave normally under the Featured sort.