Category: Saclab

  • Release Notes – Saclab General – 23.01 – Release 2.22.7 – Feb 17 09:26

    How to use this page:

    Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.

    Release

    https://cheitgroup.atlassian.net/projects/SCLB/versions/10378

    Date

    Version

    23.01 – Release 2.22.7

    Description

    Contributors

    Alexander BöhringerThư PhanAndrii Kupriianov

    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-1273

    Order summary – US – Old version: "Import duties.." block is broken

    Bug


    SCLB-1268

    Drop-ship: Email to partner once a bag is sold

    Task


    SCLB-1267

    Checkout / Apple Pay: PopUps Redesign

    Task


    SCLB-1266

    Checkout Redesign – SacLab Bug List

    CB


    SCLB-1262

    Hide Imported SKU on the website

    Task


    SCLB-1261

    Checkout – order summary – DE: Zwischensumme – if possible, fit all words in one line

    Bug


    SCLB-1260

    Checkout – previous version: phone field size and "Place order" button text don’t match the mockup

    Bug


    SCLB-1258

    Order summary – DE/ FR vesion: shipping field tag is broken

    Bug


    SCLB-1257

    Checkout: make the phone country code field mandatory

    Bug


    SCLB-1252

    Checkout: the subtotal and total fields issue while changing the LCK items count

    Bug


    SCLB-1251

    Checkout: the font weight of the "Apply coupon" button doesn’t match the mockup

    Bug


    SCLB-1249

    Checkout: the text of the title (notes field) doesn’t match the mockup

    Bug


    SCLB-1248

    Checkout – order summary: "shipping" field doesn’t match the mockup

    Bug


    SCLB-1233

    Checkout redesign

    Story


    SCLB-1110

    saclab.com Product Carousels – desktop: move starting Position

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Size (dimensions) tooltip

    As a user I want to understand what the "Size" field represents So that I can accurately interpret the item’s dimensions

    Scenario: Display size tooltip next to "Size" field

    Given I am on the product details page

    When I look at the "Size" field

    Then I should see an (i) tooltip next to it

    Screenshot 2025-02-13 at 13.09.00.png

    Scenario: Clicking on size tooltip opens item dimensions popup

    Given I am on the product details page

    When I click on the SIZE tooltip

    Then the item dimensions popup should be shown

    And it should display the item’s length, height, and width in cm for the “normal” market

    And it should display the item’s length, height, and width in in for the US market

    Screenshot 2025-02-13 at 13.15.01.png

    Scenario: Closing the item dimensions popup

    Given the item dimensions popup is open

    When I click the close (X) button or click outside of the pop-up

    Then the popup should close

  • Release Notes – Saclab General – 21.01 – Release 2.22.6 – Feb 12 16:19

    How to use this page:

    Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.

    Release

    https://cheitgroup.atlassian.net/projects/SCLB/versions/10377

    Date

    Version

    21.01 – Release 2.22.6

    Description

    Contributors

    Thư PhanAlexander Böhringer

    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-1263

    AIRTABLE product field: ID/Stamp

    Task


    SCLB-1200

    Prevent Seller Notifications When Re-Publishing Products from “Private” to “Public”

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Updating Sitemaps to include ALL [Brand + model] and [Brand + Bag Types]

    Given: I am on https://saclab.com/sitemap/

    Then: I should see a section that includes:

    4 Brand sections

    Each brand section include 2 sections for [Brand + Model] and [Brand + Bag Type] where it should list all of those links

    And when there is a new model or new bag type is added, Then this should be automatically added to the sitemaps

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9967-8244&m=dev

    Given: In the XML Sitemap
    There should be a section that includes:

    4 Brand sections

    Each brand section include 2 sections for [Brand + Model] and [Brand + Bag Type] where it should list all of those links

    And when there is a new model or new bag type is added, Then this should be automatically added to the sitemaps

  • Story 13.1.3. Bag Vault. My account

    General info

    The Bag Vault feature allows users to register and manage their luxury handbags in an organized system. The functionality includes the ability to track bags, mark them as stolen, remove them, and manage associated data. Users can submit their bags via a registration process, review details, and manage the bag’s status through different stages such as "Submitted," "Stolen," and "Removed."

    User story

    As a user of Saclab,
    I want to view my bags in personal account,
    So that I can manage and track the status of them.

    Visual design

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9811-11542&m=dev

    Acceptance criteria

    01

    Function: My Bag Vault tab
    Given I am in "My Account” section
    When I navigate to "My Bag Vault"
    Then I should see a list of all my submitted bags with their Statuses and submitted dates
    And I should have options to filter by status (Submitted, Stolen, Removed) And I should be able to select a bag to view its details

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9811-11542&m=dev

     

    image-20250205-061347.png

    02

    Scenario: Viewing a specific bag’s details

    Given I am in "My Closet" tab
    And I have selected a specific submitted bag
    Then I should see the bag’s details and available actions

     

    image-20250205-061522.pngimage-20250205-061549.pngimage-20250205-061618.png

    03

    Scenario: Marking a bag as stolen

    Given I am reviewing a specific [Submitted] bag that I have registered to my bag vault

    When: I click the "Mark Stolen" button

    Then I should see a stolen bag report form https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9848-28235&m=dev
    And when i clicked on “other notes” then a text box will appear so I can put in my note (not mandatory)

     

    When I complete the form and click "Mark Bag Stolen"
    Then the bag status is updated to "Stolen" with all provided information in AirTable and "My Closet"
    And an email is sent to our professional seller partners notifying the stolen status

    Email to partners:

    https://us12.admin.mailchimp.com/templates/edit?id=10086578

    When this stolen bag has a serial number (the users submitted it in the Serial Number input field)

    Then the system scans for the a match serial number with the field [ID/Serial number] in saclab data with both existed and new entry bag

    Screenshot 2025-02-05 at 15.17.33.png

    When a matched serial number is found

    Then an email and a slack message is sent to admin (sales@saclab.com) to report a potential stolen bag has been found

    Email:

    subject: Alert: Potential Stolen Bag Detected

    Template: https://us12.admin.mailchimp.com/templates/edit?id=10086577

    Slack message format: [Stolen Bag Alert] Potential match found between a stolen bag in the Bag Vault [Insert AirTable link] and a bag in the Product Inventory [Insert AirTable link].

    Please review and take action.

    image-20250205-061730.png

    03a

    Scenario: Marking a (marked stolen) bag as found

    Given I am reviewing a bag that was marked stolen

    When: I click the "Mark Found" button

    Then I should see a pop-up https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=10001-21274&m=dev

    And The bag status got changed from “Stolen” to “Submitted”

    Mark found promt.png

    04

    Scenario: Removing a bag

    Given I am reviewing a specific [Submitted] bag that I have registered to my bag vault

    When: I click the "Remove" button

    Then I should see a survey https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9836-6542&m=dev
    And If I chose “It was sold elsewhere” or “Other” then a text box will appear so I can put in my note (not mandatory)

    If I didn’t choose any answer but clicked “submit” then I should see the error message “Please select your answer”

    When I completed the survey

    Then the bag status is updated to "Removed" with all provided information in AirTable and "My Closet"

    image-20250205-061939.png

    05

    Scenario: User hasn’t registered any bags yet

    Given: I am logged in and is on My account

    When: I am in “My Bag Vault” section

    Then: I should see the text “You haven’t registered any bags yet” with a button “Register bag”

    Screenshot 2025-02-25 at 09.40.14.png

  • Story 13.1.2. Bag Vault. Email notifications

    General info

    The Bag Vault feature allows users to register and manage their luxury handbags in an organized system. The bag information is stored in AirTable for future reference, and notifications are sent to Saclab admins and professional sellers in case of changes in the bag’s status (e.g., when marked as stolen).

    User story

    As a user of Saclab,
    I want to receive the notification email about submitting my bag,
    So that I can understand that my bag successfully submitted and stored.

    Visual design

    Acceptance criteria

    01

    Given: I am reviewing my bag and filled all mandatory info

    When: I clicked “Submit”

    Then: The submission is submitted and the I see the thank you screen
    AND the seller receives an email “thank you for registering your bag”

    Mailchimp Email template:

    Eng:

    Subject: Thank you for registering your bag

    Preview:

    Template: https://us12.admin.mailchimp.com/templates/edit?id=10086564

     

    Ger:

    Subject: Vielen Dank, dass Sie Ihre Tasche registriert haben.

    Preview:

    Template: https://us12.admin.mailchimp.com/templates/edit?id=10086576

     

    FRE:

    Subject: Merci d’avoir enregistré votre sac.

    Preview:

    Template: https://us12.admin.mailchimp.com/templates/edit?id=10086575#f_folder:17913;f_search:view;t:files-list

    And the bag info is saved in AirTable with all the submitted information (Similar to Product inventory)

  • Story 13.1.1. Bag Vault. Registration process

    General info

    The Bag Vault feature allows users to register and manage their luxury handbags in an organized system. Users can submit their bags via a registration process. The bag information is stored in AirTable.

    User story

    As a user of Saclab,
    I want to register and manage my bags in an organized system,
    So that I can keep track of my bags and report to a network of professional sellers if my bag is stolen.

    Visual design

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9859-3075&t=PvxCf6jPPwrxltjp-4

    Acceptance criteria

    01

    Scenario: "Bag Registration" page

    Given I am on the "Bag Registration" page

    When: I am not logged in
    Then I should see the user interface with bag registration fields with the login/ register step

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9859-3075&m=dev

    The Fields: Brand, Model, Size, Main Colour and Main Material are drop-down field with the same data as our current SYB (they should be from the same data source, meaning changing one will affect both SYB interface and Bag Vault interface)


    When: I am logged in on http://saclab.com

    Then I should see the user interface with bag registration fields without the login/ register step

    Bag Vault Step 1 - not logged in.png

    Bag Vault Step 2 - not logged in.png

    02

    Scenario: User registers a new bag

    Given I complete the form and click "Submit"

    When: I am logged in
    Then I should be lead to the step “Review the bag”, And I should see a summary of the bag details I entered https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9859-3443&m=dev


    When: I am not logged in

    Then I am prompted to log in or create an account
    When I successfully log in or sign up
    Then I should be lead to the step “Review the bag”, And I should see a summary of the bag details I entered https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9799-8387&m=dev

    image-20250205-060919.png

    03

    Tickbox Function

    When: I clicked on the tickbox “I’ve read and….” or click on “terms and conditions for…”

    Then: I see the popup with the T&C opened and can be scrolled

    Let Admin can change the text and link inside the T&C any time
    (Similar to in SYB review step)

    04

    Given: I am viewing the T&C popup

    When: I click “agree and close”

    Then: The T&C pop up is closed and the tickbox “I’ve read and….” is ticked

     

    When: I click “disagree and close”

    Then: The T&C pop up is closed and the tickbox “I’ve read and….” is not ticked

    05

    Given: I am reviewing my bag and filled all mandatory info

    When: I clicked “Submit”

    Then: The submission is submitted and the I see the thank you screen
    AND the seller receives an email “thank you for registering your bag → Story 13.1.2. Bag Vault. Email notifications

  • Epic 13.1. Le Registry

    General info

    The Bag Vault feature allows users to register and manage their luxury handbags in an organized system. The functionality includes the ability to track bags, mark them as stolen, remove them, and manage associated data. Users can submit their bags via a registration process, review details, and manage the bag’s status through different stages such as "Submitted," "Stolen," and "Removed." The bag information is stored in AirTable for future reference, and notifications are sent to Saclab admins and professional sellers in case of changes in the bag’s status (e.g., when marked as stolen).


    SCLB-1299

    User stories

    Visual design

    https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=9859-3075&t=Z7qwzAFPmuC9xoJm-4

  • Update all dynamic URL links of [Brand + Model] and [Brand + Bag Types] to static URLs

    General info

    At the moment, all across the website, the old dynamic URLs of [Brand + Bag Type] and [Brand + Bag Model] are being linked to internally. These must be replaced by the static URLs.

    What needs to be done is to replace the old URL with the new one, all over the website. It could be anywhere on the website; whether on product pages or content pages.

    Acceptance criteria

    Given: An old dynamic link to [Brand + Bag Type] or [Brand + Model] still exists (anywhere on saclab.com) for example here https://saclab.com/de/bags/hermes-birkin-hss-35-taurillon-clemence-bleu-nuit-anemone/ under “Browse ALL BIRKIN”, the link is still in the old format of https://saclab.com/bags/?brand[]=hermes&model[]=birkin

    Then: This link should be replaced (not redirected but replaced) with the new format of https://saclab.com/bags/hermes/birkin/

  • Fix Crawlability Problem

    • Links in the faceted navigation are not recognized as links by Google bots.

    • HTML structure uses ul, li, label, and control elements, potentially relying on JavaScript for rendering links.

      image.png

      To fix the crawlability of links in the navigation, ensure that all links are implemented as standard HTML <a> tags with proper href attributes pointing to the correct URLs. Avoid using JavaScript or non-standard elements like <label> or <li> to simulate links, as these are not recognized by Google bots. For example, a filter option like “Hermes Birkin” should appear as <a href="/hermes/birkin">Hermes Birkin</a> instead of relying on JavaScript or checkboxes to render the link.