Category: Saclab

  • Release Notes – Saclab General – 14.01 – Release 2.22.5 – Jan 16 18:13

    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/10375

    Date

    Version

    14.01 – Release 2.22.5

    Description

    Contributors

    Thư PhanAndrii KupriianovAlexander 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-1240

    Feature: Redesign login screen post-order confirmation

    Story


    SCLB-1209

    Update Language Preference of Contact Record

    Task


    SCLB-1201

    [Bug] LIVE favourite notification bubbles: Don’t display correct amount favourites

    CB


    SCLB-1200

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

    Task


    SCLB-1190

    ApplePay method: the order wasn’t added to the "My orders" tab

    Bug


    SCLB-1151

    Auto-Link Guest Checkout Orders to Existing User Accounts by Email Matching

    Story


    SCLB-1085

    [Stage] and LIVE checkout: error message "Error Processing checkout" but order goes through

    CB

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Story 22.2. AIRTABLE product field: ID/Stamp

    General info

    The ID/Stamp field will be added to both the Product Inventory table and the SYB Submission table in Airtable.

    User story

    As an admin on saclab database
    I want to save the ID/ Stamp information
    So that it is recorded and modifiable in both the Product Inventory and SYB Submission tables.

    Acceptance criteria

    01

    Scenario 1: Admin adds ID/Stamp to “Product inventory” table

    • Given: Admin is on the “Product inventory” table

    • When: Admin adds an ID/Stamp

    • Then: The ID/Stamp is saved, and the admin can modify it at any time

    02

    Scenario 2: Admin adds ID/Stamp to “SYB submission” table

    • Given: Admin adds an ID/Stamp to the “SYB submission” table

    • When: The submission is accepted (Submission accepted = yes) and moved to the “In delivery” stage

    • Then: The value in the ID/Stamp field is saved into the “Product inventory” table, and the admin can modify it at any time

  • Story 47.1.1 Hide Imported SKU on the website

    General info

    The goal is to ensure that SKUs imported via the "Import" table in Airtable are stored internally but not displayed on the product detail page of the website.

    User story

    As a creator on Saclab Airtable,
    I want to import SKUs for products without displaying them on the website,
    So that the imported SKUs are stored internally for tracking but do not affect the website

    Acceptance criteria

    Given: I am a Creator on Saclab Airtable bases and I import the CSV file containing bag detail to “Import” table (or copy and paste the correct fields) and I moved the products to “product inventory table”

    When: The SKU is not generated or created within the product inventory table (but was imported)

    Then: The imported SKU should be stored internally (on airtable) but not displayed on the product detail page of the website (e.g https://saclab.com/bags/chanel-19-wallet-on-chain-tweed-lamb-pink/ )

  • Release Notes – Saclab General – 24.12 – Release 2.22.4 – Jan 08 09:22

    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/10362

    Date

    Version

    24.12 – Release 2.22.4

    Description

    Contributors

    Thư 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-1204

    Check loaders in the checkout

    CB


    SCLB-1188

    eMail to seller: "The Order was cancelled" sent 2 times

    CB


    SCLB-1180

    auto-adjust the filter height on the brand page

    Task


    SCLB-1175

    Pagination on the “Bags i’m selling” page

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Feature: Redesign login screen post-order confirmation

    As a customer, I want a visually improved login screen after order confirmation, So that I have a clearer and more engaging experience accessing my order.

    Given a user has an account (Account A) in the database with an email address (Email X)
    When the user successfully placed an order using guest checkout with Email X

    Then show the redesigned log in screen

    Screenshot 2024-12-23 at 01.27.07.png

    instead of (current result):

    Screenshot 2024-12-23 at 01.08.48.png

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

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

  • Story 28.4 Checkout / Apple Pay: GA4 Purchase Funnel

    General Info

    To optimize the checkout process and evaluate the impact of our redesign, we aim to enhance GA4 tracking with detailed filtering capabilities in the purchase funnel. This includes tracking behavior, abandonment points, and payment method performance while allowing segmentation between Test A (old version) and Test B (new version) as part of the A/B test. This will also allow us to find out potential problems within the user purchase flow.

    User Story

    As a business stakeholder, I want detailed tracking in GA4 for the checkout process, including user actions, abandonment points, and payment methods, so that I can evaluate the redesign’s effectiveness and improve the customer journey.

    Ga4 journeys

    Acceptance Criteria

    Acceptance Criteria

    Screenshots

    00

    Filters allow segmentation between Test A and Test B on all ACs below (except apple pay 05)

    01

    Scenario: Track logged-in vs guest checkout.
    Given: A user starts the checkout process.
    When: They proceed as logged-in or guest.
    Then: GA4 records if the user is logged in or using guest checkout
    AND displays it/lets me filter in Purchase journey + Checkout Journey

    Bildschirmfoto 2024-12-19 um 15.30.10.png

    Bildschirmfoto 2025-01-07 um 09.59.49.png

    02

    Scenario: Track entry point to checkout.

    Given: A user begins checkout.
    When: They enter via a) “Buy Now” on the product page, b) “Checkout” in the cart, or c) “Purchase” for a reserved product.  Then: GA4 tracks the entry point and lets admin filter by it in Purchase journey or similar

    Bildschirmfoto 2024-12-19 um 15.30.57.png

    03

    Scenario: Track abandonment points with field filters. Reason: track where people drop-off
    Given: A user abandons the checkout process.
    When: They abandon after filling specific fields or taking specific actions.
    Then: GA4 tracks if they:
    – Added shipping information.
    – Took an action in the payment method selection.
    – clicked “Place Order”
    And: Filters in GA4 allow viewing these specific actions.

    And: GA4 displays average time in checkout

    Bildschirmfoto 2024-12-19 um 15.32.15.png

    04

    Scenario: Track “Place Order” click success rate.
    Given: A user clicks “Place Order”.
    When: The order is completed or fails.
    Then: GA4 displays the success rate by payment method. 
    And: GA4 displays average time in checkout

    And: GA4 lets me filter by country

    05

    Scenario: Apple Pay click funnel tracking.
    Given: Apple Pay is integrated into product pages, cart, and checkout.
    When: A user clicks on the Apple Pay CTA.
    Then: GA4 tracks:
    – Apple Pay clicks on the product page, cart, and checkout.
    – How many times the Apple Pay terminal opens after the CTA click (and potential PopUp interaction in between).
    – Apple Pay terminal abandonment rate.
    – Apple Pay success rate.

    And: Filters allow segmentation between EU/GLOBAL/US Store

  • Story 12.1. Feature: Update Language Preference of Contact Record

    Content

    General info

    Users tory

    As an admin,
    I want to update the language preference of a contact record in AirTable,
    So that the selling agreement and future communications reflect the new language setting.

    Acceptance criteria

    01

    Scenario: Resend the selling agreement in the newly set language for open SYB deals

    Given a contact record exists in AirTable
    And the contact record has an open "SYB" deal linked to it (where payment has not been made to the seller)
    When I change the language preference of the contact to a new language on AirTable
    Then the selling agreement for the open "SYB" deal is re-sent in the newly set language
    And the language of the communication emails for the contact is updated to the newly set language.

    Screenshot 2024-12-10 at 13.35.27.png

    02

    Scenario: Update language for future communications

    Given a contact record exists in AirTable
    When I change the language preference of the contact to a new language on AirTable
    Then all future communication emails sent to the contact will be in the newly set language.

  • Release Notes – Saclab General – 10.12 – Release 2.22.3 – Dec 10 14:21

    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/10361

    Date

    Version

    10.12 – Release 2.22.3

    Description

    Contributors

    Filipp AntonovThư Phan

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

    [Bug] https://saclab.com/my-account/ removing favourite breaks design

    CB


    SCLB-1169

    SYB – Rework the register window (step 3 – sign up to continue)

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes