Category: Saclab

  • Release Notes – Saclab General – 03.12 – Release 2.22.2 – Dec 05 08:29

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

    Date

    Version

    03.12 – Release 2.22.2

    Description

    Contributors

    Andrii KupriianovThư 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-875

    [Marco] Purchases are not firing on the thank you page

    Investigation


    SCLB-295

    Reservation+discount: The next buyer didn’t get a discount code via email, the seller can’t create a new discount

    Bug

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Story 28.3 Checkout / Apple Pay: PopUps Redesign

    General info

    Redesign and implement updated popups for country selection and Apple Pay confirmation in the checkout flow.
    We aim to enhance the user experience and compliance by updating popups in the checkout flow. This includes improvements to country selection when switching between regions and implementing confirmation popups for Apple Pay, with specific adjustments for US customers.

    User story

    As a customer, I want clear and intuitive popups during checkout to confirm important actions, such as country selection or Apple Pay terms, so that I can proceed confidently and without confusion.

    Visual design:

    Checkout: Country selection PopUps: https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=8643-5454&t=tc4HfRjLGXOt2xcc-1

    Apple Pay PopUps: https://www.figma.com/design/6KT0tZfJw3u7R8b5pCH8vw/Saclab-Team-Library?node-id=8640-5799&t=tc4HfRjLGXOt2xcc-1

    Use our existing popup style/design to replicate the displayed popups (desktop) for the mobile version.

    Acceptance criteria

    Scenario: Country switch from EU to non-EU (excluding US)

    When: A user selects a non-EU country (or it’s auto-selected)

    Then: Show the updated popup without the tickbox

    Bildschirmfoto 2024-12-05 um 10.42.01.png

    Scenario: Country switch to the US

    When: A user selects the US as their country (or it’s auto-selected).

    Then: Show the updated popup without the tickbox

    Bildschirmfoto 2024-12-05 um 10.43.16.png

    Scenario: Country switch from US to EU

    Given: country selected as “US”

    When: A user selects a country within the EU

    Then: Display updated popup with US->EU-specific messaging

    Bildschirmfoto 2024-12-05 um 10.44.21.png

    Scenario: Country switch from US to non-EU

    Given: country selected as “US”

    When: A user selects a country outside the EU but not US

    Then: Display updated popup with US->Non-EU without the tickbox

    Bildschirmfoto 2024-12-05 um 10.47.04.png

    Scenario: Apple Pay confirmation popup (Global and EU but not US)

    When: A user selects Apple Pay and proceeds to pay (in both the checkout and the product page)

    Then: Show a mid-screen popup stating: “By using Apple Pay, you accept our Privacy Policy and Terms & Conditions.”

    Bildschirmfoto 2024-12-05 um 10.48.20.png

    Scenario: Apple Pay confirmation popup (US)

    Given: User is in the $US shop

    When: A user selects Apple Pay and proceeds to pay.

    Then: Show a mid-screen popup stating: “By using Apple Pay, you accept our Privacy Policy and Terms & Conditions.”

    Bildschirmfoto 2024-12-10 um 15.26.16.png

  • Story 28.2 Purchase Flow: Speed and UI Improvements

    General info

    We aim to enhance the speed and responsiveness of interactions such as adding items to the cart, marking favorites, and completing key actions like “Place Order” and search.

    User story

    As a customer, I want faster and more responsive interactions while browsing and checking out so that I feel confident about my purchase.

    Visual design:

    Desktop:

    Mobile

    Acceptance criteria

    01

    Scenario: Notification bubbles update instantly for “add to cart”

    When: A user clicks “Buy Now” or removes item via “X” from cart

    Then: The notification bubble updates immediately, the item disappears immedeately from cart.

    Bildschirmfoto 2024-11-27 um 11.24.54.png

    Country names EN, FR, DE for alphabetical sort:

    https://docs.google.com/spreadsheets/d/1YHTJB3gEiwuObMj8utbtRToEqTwhNk0_8PYeY5OzKv0/edit?usp=sharing

    02

    Scenario: Notification bubbles update instantly for “favorite”

    Given: A user clicks “Favourite”/Unfavourite or “Star”-Icon

    When: The action is registered

    Then: The star-icon fills in/clears instantly OR the CTA “Favourite” changes to “Unfavourite”
    And The notification bubble updates immediately.

    (even if server response is not there yet? Risk involved? Other websites are doing it)

    AR: saclab.com/bags favourite icon click: 2-3s loading time. https://app.box.com/s/u7xyfpdxp1j80pzzuulug8ugt85zo433

    Bildschirmaufnahme 2024-12-17 um 17.52.05.mov

    03

    Scenario: Increase Hitbox of “x” in cart to prevent misclicks

    Given: Cart is open

    When: User wants to remove an item

    Then: Hitbox of 10x10px” is increased to 24x24px

    Bildschirmfoto 2024-12-17 um 14.39.44.png

    04

    Scenario: Reduce animation time for cart fade-in

    Given: A user clicks on cart
    When: The cart opens
    Then: The fade-in/-out animation is 60% faster.

    Bildschirmaufnahme 2024-12-17 um 14.41.39.mov

    05

    Scenario: Reduce redirect time after “Place Order

    Given: A user clicks “Place Order”
    When: The payment is processed
    Then: The redirect time is reduced from 20s-30s to 5s.

    Screen Recording 2025-05-06 at 17.12.51.mov

    06

    Scenario: Optimize “Reserve this bag” loading

    Given: A user clicks “Reserve this bag”
    When: The request is sent
    Then: The loading time is reduced until the user gets feedback and popup “the bag has been reserved” and cartopen w product added to cart.

    Currently: 10s.
    Goal: 2s

    Bildschirmaufnahme 2024-12-17 um 14.43.24.mov

    07

    Scenario: Search bar results appear faster

    Given: A user types in the search bar
    When: Results are loaded
    Then: The loading time is reduced by 50%.
    AR: 4-5s
    ER: 2s

    Bildschirmaufnahme 2025-07-14 um 09.21.18.mov

    08

    Scenario: Filter interaction improved

    When: A user applies or removes a filter
    Then: The loading time is reduced.
    AR: 6s.
    ER: 2s

    Bildschirmaufnahme 2024-12-17 um 14.47.58.movScreenRecording_07-14-2025 09-23-22_1.MP4

    09

    Scenario: Redesign “My Account” PopUp if not logged in and Product in Cart

    Given: A Product is in Cart and User is not logged in

    When: User clicks on “Checkout” in Cart PopUp

    Then: “My account” Side-menu opens with redesigned “Guest Checkout”

    Bildschirmfoto 2024-12-17 um 18.29.11.png

  • Incident #6 [Website has been down]

    Name of incident

    Website has been down

    Date / Time

    02.12.2024 4 pm (Kyiv time)

    Request from client

    Website down

    image-20241202-170840.png

    Involved (Internal)

    Anna Aksonenko Dima Savchenko (WP) Roman Kliuiko Maxim, Honcharuk Oleh Pavlo Trukhin alex.l@cheitgroup.com

    Involved (External)

    Oliver, Alexander

    Solution

    Solution: added new rule to the Cloudflare

    image-20241202-171043.png

    Important!

    Added checkboxes (important here checkbox Security level) for including fully the rules from it:

    image-20241202-171356.png

    Conclusion how to avoid

    Leave the website in this security level “under attack“, because payments now are working

  • Release Notes – Saclab General – 28.11 – Release 2.22.1 – Nov 29 12:03

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

    Date

    Version

    28.11 – Release 2.22.1

    Description

    Contributors

    Thư PhanFilipp AntonovAndrii 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-1185

    Referrer Tracking for Orders and Submissions

    Task


    SCLB-1182

    Order > Coupon

    Task


    SCLB-1164

    SYB Restrict pick-up booking on Monday if today is Friday after 3pm

    Story


    SCLB-1143

    Bulk import. Auto-Remove Bag from Sale

    Task


    SCLB-1138

    saclab.com checkout: When I add LCK in the checkout, Phone# field clears out

    CB


    SCLB-1103

    My Orders. Do not display "Failed" Order

    CB


    SCLB-766

    Email Automations for Abandoned Products in Basket for US Customers

    Task


    SCLB-478

    Order field -> "Shipping fee"

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes

  • Referrer Tracking for Orders and Submissions

    As an Airtable user,
    I want to see the referrer information for both orders and submissions,
    So that I can analyze the traffic sources for purchases and "Sell Your Bag" submissions.

    Acceptance Criteria

    Given: A user accesses the shop via a specific source link or external website (e.g., a blog, search engine, or social media post).
    When: The user completes a purchase.
    Then: Save the HTTP Referer (if available) as part of the order record in Airtable.

    Given: A user accesses the "Sell Your Bag" page via a specific source link or external website (e.g., a blog, search engine, or social media post).
    When: The user submits a bag for selling.
    Then: Save the HTTP Referer (if available) as part of the product record in Airtable (both inventory AND submitted base)

  • Coupon field on AirTable’s order record

    As an admin, I want the voucher code used on an order to be saved in a new field on Airtable, so that I can easily track promotions applied to orders.

    Save the voucher code used on an order in a new Airtable field

    Given an order is created
    When a voucher code is applied to the order
    Then the voucher code AND its value should be shown on Airtable in the order’s record in format [VoucherCode] – [voucherValue]

    Function already exists on WooCom:

    Screenshot 2024-11-27 at 11.30.08.png

    Expected on AirT:

    Screenshot 2024-11-27 at 11.32.18.png

  • Story 28.1 Checkout Redesign

    General info

    We are redesigning the checkout to improve the user experience, streamline interactions, and enhance the overall design. The changes include improving country dropdown behavior, refining phone number inputs, and updating key UI elements.

    User story

    As a customer, I want a fast and intuitive checkout process so I can complete my purchase with ease and confidence.

    Visual design:

    Desktop:

    Mobile:

    Acceptance criteria

    01

    Scenario: Country Dropdown Functionality  Given: A user is on the checkout page. 
    Then: correct country is pre-selected based in IP (function already existing)

    When: They interact with the country dropdown.
    Then: The dropdown provides search functionality via keyboard, sorted alphabetically for EN/DE/FR. It supports Autofill.

    Bildschirmfoto 2024-11-27 um 11.24.54.png

    Country names EN, FR, DE for alphabetical sort:

    https://docs.google.com/spreadsheets/d/1YHTJB3gEiwuObMj8utbtRToEqTwhNk0_8PYeY5OzKv0/edit?usp=sharing

    02

    Scenario: Prefill country based on history or IP (already existing)

    Given: A user has past orders or IP location
    When: The checkout page loads
    Then: The country field pre-populates with the detected or historical country.

    03

    Scenario: Phone Field Design
    Given: A user selects a country in the country dropdown.

    When: They proceed to the phone field.  Then: The phone field pre-sets the country code, but the user can edit it.

    When: They edit the phone field
    Then: Use existing Phone field design with type function from SYB submission function

    Bildschirmfoto 2024-11-27 um 11.53.09.png

    Bildschirmfoto 2024-11-27 um 11.55.00.png

    04

    Scenario: Loading Wheel Optimization
    Given: A user interacts with form fields

    When: No backend data is being loaded (e.g., entering name, address, postcode, selecting payment method)

    Then: The loading wheel is removed

    05

    Scenario: Coupon field

    Given: A user checks out on mobile or desktop
    Then: The coupon field is repositioned

    Bildschirmfoto 2024-12-03 um 12.09.53.png

    Bildschirmfoto 2024-12-19 um 15.48.51.png

    06

    Scenario: Direct Bank transfer text mobile & desktop

    Given: User selects “Direct brank transfer”

    Then: Display new text AND let admin change it in WP

    Text:

    After you’ve placed your order, we’ll email instructions for making the payment via bank transfer. Your order will not be shipped until the funds have cleared in our account.

    And let admin change this text

    Bildschirmfoto 2024-12-16 um 18.29.19.png

    Scenario: A/B Test

    When: A customer reaches checkout

    Then: 50:50 A/B Test the new design (story 07 til 18) vs. the existing checkout. Performance will be tracked via Story 28.4

    Scenario: Oder Summary Desktop

    Given: A user checks out

    When: They view the order summary

    Then: Redesign, Bigger Text field in case of long product name, Grade Included, USPs included

    AND When: User scrolls down

    Then: Order summary floating/sticky. visible in Prototype

    Bildschirmaufnahme 2024-12-19 um 15.51.41.mov

    Bildschirmfoto 2024-12-19 um 15.50.02.png

    07.1

    Scenario: Oder Summary Mobile €

    Given: A user checks out with € value

    When: They view the order summary

    Then: Redesign, Bigger Text field in case of long product name, Grade Included

    AND When: User scrolls down

    Then: “Total” sticky on top of page. Visible in Prototype

    Bildschirmfoto 2024-12-16 um 18.02.18.png

    Bildschirmaufnahme 2024-12-16 um 18.12.01.mov

    7.2

    Scenario: Oder Summary US desktop

    Given: A user checks out with $US value

    When: They view the order summary

    Then: Redesigned Order Summary AND More product details are displayed AND user sees $ value AND info text “Import duties & fees included” AND bottom text “returns not possible”

    AND When: User scrolls down

    Then: floating Order Summary

    Bildschirmfoto 2024-12-23 um 13.06.48.png

    Bildschirmfoto 2024-12-23 um 13.08.10.png

    07.2

    Scenario: Oder Summary US mobile

    Given: A user checks out with $US value

    When: They view the order summary

    Then: Redesigned Order Summary AND More product details are displayed AND user sees $ value AND info text “Import duties & fees included” AND bottom text “returns not possible”

    AND When: User scrolls down

    Then: “Total” sticky on top of page

    Bildschirmfoto 2024-12-16 um 18.14.09.png

    Bildschirmfoto 2024-12-23 um 13.09.56.png

    08

    Scenario: USPs on mobile

    Given: A user is in the checkout on mobile

    When: The user scrolls to the bottom of the page

    Then: USPs are displayed

    Bildschirmfoto 2024-12-19 um 16.35.26.png

    09

    Scenario: Top Bar on mobile

    Given: A user visits the checkout on mobile

    Then: New Reviews.io badge is displayed AND “Secure Payment” Text AND Saclab Logo AND Payment methods displayed. No more display of Navigation bar

    Bildschirmfoto 2024-12-19 um 16.36.13.png

    10

    Scenario: Top Bar on Desktop

    Given: A user visits checkout on deskto

    Then: New http://Reviews.io badge is displayed AND “Secure Payment” Text AND Saclab Logo (already existing) AND Payment methods (already existing) displayed.

    Bildschirmfoto 2024-12-19 um 16.39.43.png

    11

    Scenario: Bottom text Reposition

    Given: A user enters checkout on desktop on mobile

    When: A user scrolls down

    Then: Text “your personal data…” is repositioned. The Text still differs between the EU/US version

    Bildschirmfoto 2024-12-19 um 16.41.39.png

    Bildschirmfoto 2024-12-19 um 16.44.30.png

    12

    Scenario: CTA “Pay Now”

    Given: A user is in the checkout on mobile or desktop

    Then: Change Cta from “PLACE ORDER” to “PAY NOW”

    Bildschirmfoto 2024-12-19 um 16.46.43.png

    13

    Scenario: Text input fields redesign

    When: a user visits the checkout on mobile or desktop

    Then: The text input fields are repositionend/redesigned to slim down the page

    Bildschirmfoto 2024-12-19 um 16.23.19.png

    Bildschirmfoto 2024-12-19 um 16.24.38.png

    14

    Scenario: Mandatory field “State”/”County”

    Given: A user checks out on mobile or desktop

    When: Country is selected where field “State” is mandatory (by wooC)

    Then: Desktop: Display “State” like displayed here. Mobile: Display “State” like displayed here.

    When: Country is selected where field “State” is not mandatory

    Then: do not display field “State” at all (on mobile and desktop)

    (function already existed)

    Bildschirmfoto 2024-12-19 um 16.14.34.png

    Bildschirmfoto 2024-12-19 um 16.20.29.png

    16

    Scenario: Display payment methods in a specific order based on country and order value.
    Given: A user reaches the payment step during checkout.
    When: The payment methods are displayed.
    Then: The payment methods are ordered as follows, based on “Country” selected:
    Germany, Austria:  1. Direct Bank Transfer  2. Credit Card  3. PayPal
    All other countries AND Order value < €20,000:  (1. Bancontact  2. iDEAL)  3. Credit Card  4. Direct Bank Transfer  5. PayPal
    All other countries AND Order value > €20,000:  (1. Bancontact  2. iDEAL)  3. Direct Bank Transfer  4. Credit Card  5. PayPal
    And: The first payment method in the list is automatically pre-selected.

    16.1

    When the user’s language is French and the order value is < 20,000€ (function already existed – no A/B testing here)

    then: Direct bank transfer payment method is disabled

    17

    Scenario: The user wants a different billing address

    Given: The user is in the checkout

    When: The user wants to input the shipping address

    Then: Default address fields are now the SHIPPING address fields. The user can click the checkbox for different billing address.

    Bildschirmfoto 2024-12-19 um 17.38.11.png

    18

    Scenario: Suggestion from hipay: The user is unsure about the term “Credit Card” and wants to pay with her card

    Given: User is in checkout

    Then: User sees “Card Payment” as Payment Option, instead of “Credit Card”

    And Admin sees payment method still as “Credit Card” in WooC Order

    Screenshot 2025-01-16 at 12.41.20.png

  • Epic 28. Checkout / Purchase Flow

    General info

    General description

    Epic ticket:

    User stories

    Visual design

    Desktop:

    Mobile: