Skip to content

1.11.15

βš™οΈ Patch 1.11.15 β€” FBA: multiple seller SKUs per ASIN

πŸš€ Summary

FBA sync no longer drops a second Amazon listing when one ASIN has multiple seller SKUs. Each extra merchant SKU gets its own article + fba_details row so both listings stay in the system and can be recalculated / exported to Sellerlogic.

✨ Details

Area Behavior
Multi-listing sync First listing keeps repricer_articles.sku = ASIN. Additional seller SKUs create a sibling article (sku = seller_sku) with its own fba_details (asin set)
No overwrite Sync no longer replaces an existing listing’s seller_sku when another merchant SKU shares the same ASIN
Buy price Sibling articles still resolve buy price via fba.asin β†’ shopping table (same as ASIN-keyed rows)
Recalc / export Each sibling has its own FBA detail β†’ independent min/max, status, and Sellerlogic export

Example (ASIN B0C41NF8K6):

Article SKU fba.seller_sku fba.asin
B0C41NF8K6 J3-DXH8-E326 B0C41NF8K6
65-N1KW-Z6QO 65-N1KW-Z6QO B0C41NF8K6

πŸ“Œ Notes

  • Redeploy service-multi-repricer.
  • Run an FBA sync (all or the affected ASIN) so missing sibling listings are created.
  • Docs: FBA articles endpoints.

βœ… Verify

  1. Sync FBA for an ASIN that has two Sellerlogic listings (e.g. B0C41NF8K6).
  2. Both seller SKUs appear in the FBA tab (one row with article SKU = ASIN, one with article SKU = second seller SKU).
  3. Recalculate + export updates both listings in Sellerlogic (no overwrite of the other SKU).

πŸ“ Files

  • backend/service_multi-repricer/app/api/v1/endpoints/fba_articles.py β€” sibling article for extra seller SKU
  • backend/service_multi-repricer/app/tests/test_fba_multi_seller_sku.py β€” unit test
  • docs/docs/services/service_multi_repricer/endpoints/fba_articles.md β€” sync note
  • docs/docs/patchnotes/1.11/1.11.15.md β€” this file