# USS (Scanuss) Package Scanning USS (provided by **LIMITED STORE, s.r.o.** at [scanuss.com](https://scanuss.com)) is an external package-scanning service integrated directly into the **Label Dialog**. After you generate a UPS label, you can send it to USS to have the shipment's scan signal sent to the carrier on your behalf. ## What is a USS scan? When you sell on platforms like StockX or Alias, you typically have **2 business days** to ship before your order is flagged as late. USS extends that window to **5–7 business days** by registering your UPS label with the carrier ahead of physical dispatch. * **How it works** — USS sends a data signal tied to your label to the carrier's system, which the platform reads as confirmation your shipment is in motion. * **What you gain** — extra time to consolidate orders, source inventory, or arrange logistics without triggering a late-shipment penalty on your seller account. * **What it is not** — a substitute for shipping. You are still required to physically dispatch the parcel within the deadline that follows the scan (see [Shipping deadlines](#shipping-deadlines) below). ## Where it lives in the tool

The Label Dialog with the USS integration — note the USS pill in the top toolbar (link state + credit balance), the Scan pill column on each row, and the per-box Send to USS / Scanned indicators in the Bulk Boxes panel.

The integration adds three things to the Label Dialog: * A **USS header pill** at the top of the right panel showing your link state and remaining credits. * A **Scan column** on each row, displaying a per-label USS status pill. * New **context-menu actions** (right-click a row): *Send to USS*, *Refresh USS status*, *Open USS dashboard*. {% hint style="warning" %} USS is a third-party service with its own [Terms and Conditions](https://scanuss.com). By using the integration you agree to those terms — most importantly, that you **physically possess the shipment** at the moment of scanning and will dispatch it within the deadline (see *Shipping deadlines* below). {% endhint %} ## Linking your account USS is tied to your Discord account. Before you can submit any label you need to link RestocksAIO to USS. 1. Open the **Label Dialog** and look at the top of the right-hand panel — the strip labelled **USS:** with a `—` balance is the entry point. 2. Click the strip. Because you are not yet linked, the tool opens the USS Discord OAuth page in your default browser. 3. Authorize with the same Discord account you use to log in to RestocksAIO. USS sends a callback back to the tool once the OAuth flow completes. 4. Once linked, the header pill switches to show your **credit balance** and clicking it again refreshes the balance. {% hint style="info" %} USS uses your RestocksAIO Discord UID as the account identifier — the same account you log in with. There is no separate username/password. {% endhint %} {% hint style="warning" %} If the link callback does not fire (firewall, browser hijack, etc.), close and reopen the Label Dialog after authorizing — the tool will pick up the linked state on the next session refresh. {% endhint %} ## Eligibility A row can be sent to USS only when **both** of these are true: * **Carrier is UPS** — USS only handles UPS shipments today. * The row has a **valid tracking number** (not empty, not `untrackable`). Rows that do not meet these conditions show a **No Tracking** or **Non-UPS** pill in the Scan column and cannot be submitted. If you bulk-select a mix of eligible and ineligible rows, the ineligible ones are skipped and counted in the confirmation dialog. {% hint style="danger" %} USS prohibits use for **peer-to-peer transactions** (Vinted, eBay, Facebook Marketplace, etc. — anything sent directly to a consumer). The service is intended for logistics flows to platform verification centres only. Misuse can result in your USS account being blocked without refund. {% endhint %} ## Sending labels to USS You can submit either a **single row** or a **bulk selection**. ### From the Scan-column pill Click the **Send to USS** pill on any eligible row. If you have multiple rows checked *and* the row you clicked is one of them, the tool treats the action as a **bulk submit** for all checked rows. Otherwise it submits just the clicked row. ### From the right-click menu Right-click any row (or a selection of checked rows) and choose **Send to USS**. The same single-vs-bulk rule applies: if more than one row is checked the action targets the whole checked set. ### Picking a region USS needs to know which courier region to dispatch through (e.g. `UPS - Germany`, `UPS - Italy`). The tool loads the available regions from USS on first use and caches them. * If only **one region** is available, it is selected automatically. * If **multiple regions** are available, a small popup appears next to the pill/menu — pick the region you want. ### Confirmation Every submission — single or bulk — opens a **confirmation dialog** showing: * The number of labels being submitted. * The selected region. * The credit cost (USS charges **1 credit per label**). * Your current available credits. This dialog is mandatory: USS deducts credits per order, so the tool never submits without explicit confirmation. After you confirm, the tool submits each row to USS and updates the Scan-column pill as responses come back. A snackbar summarises successes, failures, and any rows skipped for ineligibility or insufficient credits. ## Status pill values The Scan-column pill reflects the current USS state for the row: | Pill | Meaning | | ---------------------- | ------------------------------------------------------------------------------------------------- | | **No Tracking** | The row has no tracking number — cannot be submitted. | | **Non-UPS** | Carrier is something other than UPS — not supported by USS. | | **Send to USS** | Eligible but not yet submitted — clickable to submit. | | **Pending** | Submitted; USS has accepted the order and is waiting for handoff. | | **Processing** | USS is processing the package. | | **Scanned** | The scan signal has been sent successfully. Triggers a Discord/Telegram notification (see below). | | **Shipped** | The package has been dispatched. | | **Cancelled / Voided** | The order was cancelled or voided on the USS side. | | **Failed** | Submission failed — check the snackbar for the reason. | ## Refreshing status USS state lives on the USS server, not in your local database. The tool hydrates submitted orders when the Label Dialog opens, and you can also force a refresh: * **Right-click → Refresh USS status** — re-fetches the latest status from USS for the selected rows. Works on any row that has a tracking number, even if you submitted it through a previous session. * **Click the USS header pill** when linked — refreshes your credit balance. When a row transitions from **Pending/Processing → Scanned** during the active session, the tool sends a notification through your **Labels Discord webhook** and **Telegram label-notification** channel (if configured). Orders that are already Scanned at the time of the initial dialog hydration do not re-notify. ## Shipping deadlines USS requires that you physically dispatch every scanned shipment within a fixed deadline: * **Alias** sales: **3 business days** (Saturdays count) from the scan. * **All other platforms** (StockX, etc.): **5 business days** from the scan. You can request a paid deadline extension directly from USS (charged at **0.5 credits per day**, paid in advance via the USS dashboard). Missing the deadline without an extension triggers a contractual penalty (0.5 credits per day late) and, on repeated violations, can lead to your USS account being blocked. {% hint style="info" %} The deadline starts the moment the scan signal is sent — that is, when the row reaches **Scanned** status, not when you click *Send to USS*. {% endhint %} ## Credits, top-up & dashboard * **Minimum purchase:** 3 credits. **1 credit = 1 scan attempt.** * **Expiration:** unused credits expire **12 months** after purchase. * **Refunds:** credits are non-refundable except for technical defects on the USS side. Rejections caused by platform/carrier API changes, IP detection, or account flags do **not** qualify for a refund. * Click **Open USS dashboard** in the right-click menu — opens `scanuss.com/dashboard` in your browser, where you can buy credits, request deadline extensions, and review your full order history. * The header pill always reflects your latest known balance; click it to force a refresh after topping up. ## Troubleshooting | Problem | What to check | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | *"USS regions not loaded yet"* snackbar | The region list is fetched on link — wait a moment and retry; the tool will auto-retry up to 4 times. | | *"Insufficient USS credits"* | The bulk selection costs more credits than you have. Top up at scanuss.com/dashboard or reduce the selection. | | *"No eligible UPS rows with tracking to submit"* | None of the selected rows are UPS + have a non-empty tracking number. | | Pill stays on **Pending** for a long time | Right-click → **Refresh USS status** to pull the latest state from the USS server. | | Scan rejected by the marketplace / carrier | Per the USS T\&Cs this is not refundable — platform-side patches, IP detection, and account flags are outside USS's control. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.restock.gg/features/functions/uss-package-scanning.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.