01

When I am a Creator on Saclab Airtable bases

Then I can import CSV files or copy and paste bag details to “Import” table

02

Scenario: Upload Bag Item Details on “Import” AirTable

Given: I am a Creator on Saclab Airtable bases and I have access to the CSV file with the correct template for bag upload

When: I import the CSV file containing bag detail to “Import” table (or copy and paste the correct fields)

Then: the system should add each bag to the "Import" table

And the SKU should be set according to the CSV file provided (might not be the same format as ours) AND this does not mess up with our current SKU generation function

AND if the SKU field is empty Then the SKU should be automatically generated

And the shelf location should be determined from the CSV

And other available details (e.g brand, model, price, contact, O/C (=drop-ship) etc.) should be set according to the csv file

And there should be a field “Import to main table”

Given: I am a Creator on Saclab Airtable

When: I ticked on the filed “Import to main table”

Then: Bag(s) is “moved” to the table “Saclab Inventory” (with all its available detail such as Brand, model, etc.)

And the bag has status “Not Photographed”

And a Deal is created on Hubspot with the associated contact and respective details

And a product is created on WooCommerce (with private status) with respective details

And the bag is shown in the seller’s “Bags I’m selling” section

03

Scenario: When the bag is sold (Drop-ship)

Given: a bag with the O/C field set to “Drop-Ship”

Then: the normal SYB flow does not apply to this bag and email such as “we have received your bag”, “we have updated the details of your bag”, etc. should not be sent to the seller

When: this bag is sold

Then: a message should be sent to the #bag-sales Slack channel indicating the sale as Bag sold: DROP-SHIP – SKU Bag name

And an email should be sent to the appointed Partner Coordinator to inform them about the sale including the SKU, bag name, price sold etc. (specified more below)

And an email should be sent to the external partner (set as contact) confirming the sale of the bag

And the order should be recorded in the systems as a "normal" flow

03.1

When: this bag (in scenario 3) is sold

Then an email should be sent to the external partner (set as contact) confirming the sale of the bag, this email should include

Order Number:

SKU:

Payout:

Payment status:

+ Awaiting Payment = if the order status is On Hold

+ Payment completed = order status is Processing

+ Payment canceled = order status is canceled

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

Subject: Bag [SKU] has been sold

03.2

Given: this bag (in scenario 3) was sold and was awaiting payment (order status = on hold)

When: the payment is received (order status reaches “Processing”)

Then: an email should be sent to the external partner (set as contact) confirming the payment was received

Subject: Bag [SKU] sale update – payment received

Mailchimp template: https://us12.admin.mailchimp.com/templates/edit?id=10086540

03.3

Given: this bag (in scenario 3) was sold and was awaiting payment (order status = on hold)

When: the order status changed to canceled (e.g 7 days passed and the payment did not arrive)

Then: an email should be sent to the external partner (set as contact) confirming that unfortunately the sale of this bag failed and the bag is back online

Subject: Order canceled for bag [SKU]

Mailchimp template: https://us12.admin.mailchimp.com/templates/edit?id=10086541

03.4

Given: this bag (in scenario 3) is sold

When the WooC Order Status is “pending payment”
Then do not send the email “bag was sold” (in scenario 3.1) to the partner

04

Scenario: Remove Bag from Sale

Given an email is received in the sales@saclab.com inbox from the external partner stating a drop-ship bag has been sold on their site

When the email content bag’s SKU and name and that it has been sold

Then the bag should be treated as it was removed by the seller (9.1) meaning the bag should be automatically moved to “Removed by seller” etc…

05

And for all other sales scenarios, the flow should follow our current processes