Back to Home

Merchant Signup

Request access to ERP — your in-stock inventory books that sync listed SKUs to the AISiliconV marketplace (not a public RFQ bulletin board).

  • After approval you receive a supplier password for sign-in.
  • Sign in opens /supplier/workspace — choose ERP or Limited-time BID. Purchases and sales are ERP tabs, not separate workspaces.
  • Listed stock is shared; unit cost and unlisted warehouse SKUs stay private.

Compliance documents (required, up to 1MB each)

Accepted file types: PDF, JPG, PNG, WEBP.

Customer Agreement (required)

AISiliconV Customer Agreement2026-10-20

This AISiliconV Customer Agreement (version 2026-10-20) takes effect when a customer registers. Submitting a registration means the customer has read and agreed to it. It covers viewing stock, bidding, closing a deal, receipt, inspection, shipment, and pickup on the AISiliconV open market. A written order may add delivery and payment detail. In the ERP workspace, company profile fields and listed inventory are visible to members; unit cost and financial books stay private. Buyer purchase demand is matched internally.

1. Misrepresented inventory

1.1 Reports and evidence

  1. If a buyer or other interested party reports that listed inventory does not match real fulfilment ability, the platform may open a review.
  2. When the platform asks the supplier to explain, the supplier must, by the deadline given, submit materials showing the conduct is not bad-faith false inventory. Materials may include proof of title, in-transit or available-to-pickup evidence, production or order records, and correspondence with the buyer, as described in the evidence guide the platform sends.
  3. If the supplier has no good reason for missing the deadline, or the evidence does not remove a fair suspicion of bad-faith false inventory, the platform may restrict listings, freeze settlement, or suspend the account. Serious or confirmed cases may end the cooperation permanently.

1.2 Take the SKU down when the listing is in doubt

When quantity, lot, or lead time may clearly disagree with the listing, stock integrity is in question, or anything else would weaken the belief that “in stock” means “can ship as promised,” the customer takes the SKU down or pauses new orders within one hour of learning of it or of a platform prompt.

This is an operating requirement. The platform still assigns responsibility from its review.

2. Inspection, shipping, and payment

2.1 Ship after inspection

Goods complete AISiliconV’s agreed inspection before the platform, or a path the platform designates, ships them. A customer does not ship straight to the end customer to skip inspection unless a separate written agreement exists and the platform accepts that exception.

2.2 Payment milestones

Unless that order says otherwise in writing, the goods price is paid in two steps:

  1. First 50%: after the platform inspects the goods and releases them under the order.
  2. Remainder: 7 business days after the goods reach the end customer and delivery is complete, using the agreed proof of receipt or traceable logistics.

Currency, bank details, invoice, and tax follow each order or purchase contract.

3. Platform fee

For every transaction on the platform, the fee is charged only after both of these are done: the platform has received the goods and finished inspection, and the goods have shipped, or pickup is complete.

The fee is a 50 USD processing charge per transaction, plus 1.88% of the goods value. Goods value is the confirmed price of the goods and does not include this platform fee.

The fee is calculated in US dollars. It is separate from the amount paid to the supplier. Registering means the customer agrees to pay it on these terms.

4. Inspection scope and post-install disputes

4.1 Pre-shipment verification

The platform follows its published quality standard for pre-shipment authenticity checks: visual inspection, marking comparison, and limited sampling such as X-Ray or Decap where the program allows. A pass means the goods cleared authenticity-oriented checks for obvious counterfeit or refurbishment signs and abnormal packaging.

This check is not an OEM or authorized-factory failure analysis. The platform does not take OEM-level responsibility for long-term reliability in every end application, latent defects, or field failures from design margin, ESD, mishandling, supply outside the sampled units, or environmental stress after delivery.

4.2 Logistics path

  1. The supplier delivers the goods to AISiliconV.
  2. AISiliconV runs the agreed inbound inspection.
  3. After release, goods ship to the buyer on the contracted route. Pickup is completed at the agreed desk. A written exception is the other case.

4.3 A buyer reports that mounted parts do not work

  • Path A: an authoritative lab shows counterfeit or refurbishment, or a condition the verification should have screened, and the pre-shipment report should have flagged it under the published standard. The buyer receives the refund the order requires. The platform recovers from supplier collateral as agreed. Compensation stays within what this agreement and that order state.
  • Path B: verification still supports genuine parts, and the buyer reports a functional or application fault. The platform sends the archived raw inspection record to the supplier or OEM for failure analysis. The platform keeps the evidence and coordinates. It does not automatically pay for application-level faults.

Timing, laboratories, refund math, deposits, and notices are applied together with this agreement and that order.

5. Quality warranty

  1. For goods traded on this platform, the supplier provides at least 60 days of quality coverage.
  2. Unless the order says otherwise, the warranty runs from end-customer receipt or from delivery completion confirmed by the platform, using the start the order selects.
  3. Exclusions, returns, and inspection follow that order and product type. The 60-day minimum still applies.

6. Zero tolerance

Confirmed bad-faith false inventory, counterfeits, or fraud permanently remove that customer’s ability to sell here. The platform delists the goods, closes the account, and may take legal or referral steps. Existing orders follow this agreement and applicable law.

7. Version

This agreement is version 2026-10-20. The registration record stores the version and the time the customer accepted it. A later version applies to new transactions after the customer accepts that version.

Already have a merchant password? Go to Merchant Sign In
AISiliconV Customer AgreementClick to expand▾

AISiliconV Customer Agreement2026-10-20

This AISiliconV Customer Agreement (version 2026-10-20) takes effect when a customer registers. Submitting a registration means the customer has read and agreed to it. It covers viewing stock, bidding, closing a deal, receipt, inspection, shipment, and pickup on the AISiliconV open market. A written order may add delivery and payment detail. In the ERP workspace, company profile fields and listed inventory are visible to members; unit cost and financial books stay private. Buyer purchase demand is matched internally.

1. Misrepresented inventory

1.1 Reports and evidence

  1. If a buyer or other interested party reports that listed inventory does not match real fulfilment ability, the platform may open a review.
  2. When the platform asks the supplier to explain, the supplier must, by the deadline given, submit materials showing the conduct is not bad-faith false inventory. Materials may include proof of title, in-transit or available-to-pickup evidence, production or order records, and correspondence with the buyer, as described in the evidence guide the platform sends.
  3. If the supplier has no good reason for missing the deadline, or the evidence does not remove a fair suspicion of bad-faith false inventory, the platform may restrict listings, freeze settlement, or suspend the account. Serious or confirmed cases may end the cooperation permanently.

1.2 Take the SKU down when the listing is in doubt

When quantity, lot, or lead time may clearly disagree with the listing, stock integrity is in question, or anything else would weaken the belief that “in stock” means “can ship as promised,” the customer takes the SKU down or pauses new orders within one hour of learning of it or of a platform prompt.

This is an operating requirement. The platform still assigns responsibility from its review.

2. Inspection, shipping, and payment

2.1 Ship after inspection

Goods complete AISiliconV’s agreed inspection before the platform, or a path the platform designates, ships them. A customer does not ship straight to the end customer to skip inspection unless a separate written agreement exists and the platform accepts that exception.

2.2 Payment milestones

Unless that order says otherwise in writing, the goods price is paid in two steps:

  1. First 50%: after the platform inspects the goods and releases them under the order.
  2. Remainder: 7 business days after the goods reach the end customer and delivery is complete, using the agreed proof of receipt or traceable logistics.

Currency, bank details, invoice, and tax follow each order or purchase contract.

3. Platform fee

For every transaction on the platform, the fee is charged only after both of these are done: the platform has received the goods and finished inspection, and the goods have shipped, or pickup is complete.

The fee is a 50 USD processing charge per transaction, plus 1.88% of the goods value. Goods value is the confirmed price of the goods and does not include this platform fee.

The fee is calculated in US dollars. It is separate from the amount paid to the supplier. Registering means the customer agrees to pay it on these terms.

4. Inspection scope and post-install disputes

4.1 Pre-shipment verification

The platform follows its published quality standard for pre-shipment authenticity checks: visual inspection, marking comparison, and limited sampling such as X-Ray or Decap where the program allows. A pass means the goods cleared authenticity-oriented checks for obvious counterfeit or refurbishment signs and abnormal packaging.

This check is not an OEM or authorized-factory failure analysis. The platform does not take OEM-level responsibility for long-term reliability in every end application, latent defects, or field failures from design margin, ESD, mishandling, supply outside the sampled units, or environmental stress after delivery.

4.2 Logistics path

  1. The supplier delivers the goods to AISiliconV.
  2. AISiliconV runs the agreed inbound inspection.
  3. After release, goods ship to the buyer on the contracted route. Pickup is completed at the agreed desk. A written exception is the other case.

4.3 A buyer reports that mounted parts do not work

  • Path A: an authoritative lab shows counterfeit or refurbishment, or a condition the verification should have screened, and the pre-shipment report should have flagged it under the published standard. The buyer receives the refund the order requires. The platform recovers from supplier collateral as agreed. Compensation stays within what this agreement and that order state.
  • Path B: verification still supports genuine parts, and the buyer reports a functional or application fault. The platform sends the archived raw inspection record to the supplier or OEM for failure analysis. The platform keeps the evidence and coordinates. It does not automatically pay for application-level faults.

Timing, laboratories, refund math, deposits, and notices are applied together with this agreement and that order.

5. Quality warranty

  1. For goods traded on this platform, the supplier provides at least 60 days of quality coverage.
  2. Unless the order says otherwise, the warranty runs from end-customer receipt or from delivery completion confirmed by the platform, using the start the order selects.
  3. Exclusions, returns, and inspection follow that order and product type. The 60-day minimum still applies.

6. Zero tolerance

Confirmed bad-faith false inventory, counterfeits, or fraud permanently remove that customer’s ability to sell here. The platform delists the goods, closes the account, and may take legal or referral steps. Existing orders follow this agreement and applicable law.

7. Version

This agreement is version 2026-10-20. The registration record stores the version and the time the customer accepted it. A later version applies to new transactions after the customer accepts that version.