team should work with PC, who can refer to a lab where required

Below options can be explored:
1. Work with Finance and DI Program to co-bear compliance costs with the vendor for first year of launch
2. Explore copy compliance if it exists in EU so that vendor does not need to invest on compliance costs
3. Work with vendor to ensure we are performing maximum grouping of ASINs to have multiple ASINs covered under single certificate
4. Explore if we can also launch non-regulated selection part of vendor portfolio , so that the %investment on COGS related to compliance reduces for the vendor

DR team communicates to vendors through paragon cases, for which access is restricted to VMs. As a workaround, we have aligned with DR team to add DIP VMs in proactive reach-outs to vendors.
VMs can reach out to Document Review (DR) team POCs for support (fmalabe@, Mo'men under Judy Jin's team)

For DI Core, the current acceptable confidence score for WW geographies is 0.97 , meaning 97% accuracy score. The higher the confidence score is, the more accuracte the classification is.
When ASINs are injected for automated classification, the output of those ASINs also provides a confidence score along with HTS code.
CustomML output provides an output of 0.955 (95.5% accuracy) and can be performed by ingesting ASINs in bulk with STL team (shabeek@)

The alignment with GSRC team is to provide an output for TC and PC within 7 days of request, and delays beyond the timeline can be escalated. There maybe exceptional circumstances where the backlog maybe higher, leading to a higher wait time.

Brand wise classification status for AE and SA.txt
ASIN wise or brand wise TC/PC can be checked using the above query.
For ASINs that do not have a TC or a PC output, those would be picked up by GSRC team through PO listener queue automatically.
For ASINs that are missing TC/PC and are not part of PO listener queue, need to be raised through manual classification SIMs.

Test reports basis the product_types can be referred in compliance handbook.
All test reports should be issued from an ISO 17025 accredited lab following AE testing standards. We may always connect you the labs (SGS or BV) who can support with the testing AE - SA Compliance Handbook.xlsx

VM can raise an investigation request using the SIM: https://t.corp.amazon.com/D294524250 or reach out to compliance PM caroljin@.
This usually happens when the ASIN is on PO but the PC classification for the ASIN is not yet completed or published on Ratchit

1. Cost of compliance is supposed to be borne by the vendors, unless there has been an alignment to co-bear some of the compliance costs with the vendor
2. The speed of response from labs depends on vendor ability to provide the right test reports on time, where we usually see back and forth. If all requirements are provided correctly, labs typically confirm the status in maximum 2 weeks time.
Delays pertaining to labs should be escalated to PC team POC : Badr Alromikhan

copy compliance is automatically applied where applicable. It is where we use existing documents from another MP for the specific ASIN to approve an ASIN

An ASIN maybe subject to multiple norms by internal teams that work on customer safety viz. DG (Dangerous Goods), Hazmat, etc. TSE (Trustworthy Shopping Experience) team is one such team that works on implenting right safety norms for selection that we offer to customers. The scope of Product compliance and TSE may be different and we can have instances where restrictions are applied to produce by TSE which are unblocked by PC, and vice versa. Solutioning for such scenarios needs to be independently completed with the respective team

not in scope of GTS

GTS-PC set the bases for PT calssification by having a Quick Reference Document (QRD) for each PT. Classifiers will check the details and characteristics of each ASIN basis description and bullet points, and will decide which PT applies. In some cases, the classification might be different between SA and AE due to the difference in the local requirements and governmental enforcements in each MP.
When a request is raised for PC classification through PO listener or VM request, ASINs are subject to auto-classification checks. Approximately 60% of ASINs automatically get assigned a PT, remaining 40% of ASINs are injected for manual classification

reviewed in training,

Each product should have the COO mentioned on the prodcut in the format Made in XXX along with other labelling requirements

out of scope for PC, should be discussed with retail