FBN and Crossdock B2B Received Reports
The FBN and Crossdock B2B Received Reports are essential tools for tracking the total stock received by Noon from sellers under the FBN (Fulfilled by Noon) or FBP (Fulfilled by Partner) models. These reports allow sellers to monitor product reception, identify discrepancies, and address QC (Quality Control) issues effectively. This guide explains how to access the reports, understand their structure, and leverage them for key use cases.
How can I access the report?
Follow these simple steps to access the FBN Received Report or Crossdock B2B Received Report in Seller Lab:
- Navigate to Reports:
-Click the three lines at the top-left corner of the screen.
-Go to Reports and select Custom Reports.
- Generate the Report:
-Click on Generate Report.
-Choose the report you need:
i.FBN Received Report
ii.Crossdock B2B Received Report (Legacy)
- View or Download:
-Use the report directly within the Seller Lab interface.
-Alternatively, download the report in Excel (CSV)
format for further analysis.
Understanding the Reports
1. Crossdock B2B Report Structure
The report takes in a from date and a to date as input parameters. The report shows the B2B received items where the ASN Created at is within the given date range.
|
Column Name |
Meaning |
Is Hidden Initially |
Is Grouppable |
|
Partner SKU |
The psku of the product created by the partner |
|
Yes |
|
SKU |
The Noon SKU the psku is mapped to |
Yes |
Yes |
|
Brand |
The brand of the product |
Yes |
Yes |
|
Product Title |
The name of the product |
|
|
|
ASN |
The ASN in which the product was received |
|
Yes |
|
Noon Warehouse Code |
The partner warehouse code from which the product was received |
Yes |
|
|
Partner Warehouse Code |
The partner code from which the product was received |
Yes |
|
|
Country Code |
The country in which the ASNs are received in |
Yes |
|
|
Expected Qty |
The quantity of the product expected |
|
|
|
Received Qty |
The quantity of the product received |
|
|
|
QC Failed Qty |
The quantity of the product received but failed the QC Checks |
|
|
|
Not Received Qty |
The quantity of the product not received (Expected - Received Qty) |
|
|
|
Unidentified Qty |
The quantity of the product that was marked as unidentified |
|
|
|
QC Failed Reason |
The reason why a product has failed the QC Check |
|
Yes |
|
ASN Created At |
The date the ASN was created at |
|
|
- To
find out how much units you have received under a particular PSKU
- To find out how much units you have received under a particular ASN
- To find out which products have had the most QC Fails for a particular time period
- To find out which products were not received over a particular time period
- To find out which the total number of unidentified products over a particular time period
2. FBN Report Structure
The report takes in a from date and a to date as input parameters. The report shows the FBN received items where the ASN Created at is within the given date range.
|
Column Name |
Meaning |
|
Partner SKU |
The psku of the product created by the partner |
|
SKU |
The Noon SKU the psku is mapped to |
|
Pbarcode |
The barcode of the product created by the partner |
|
storage_type_code |
The type of item example high retail value(hrv) |
|
Brand |
The brand of the product |
|
Product Title |
The name of the product |
|
ASN |
The ASN in which the product was received |
|
Noon Warehouse Code |
The noon wh code in which the product/s was/were received |
|
Partner Warehouse Code |
The partner warehouse code from which the products were sourced |
|
Country Code |
The country in which the ASNs are received in |
|
Expected QTY |
The quantity of the products scheduled on the ASN |
|
Received Qty |
The quantity of the product received |
|
QC Failed Qty |
The quantity of the product received but failed the QC Checks |
|
Unidentified Qty |
The quantity of the product that was marked as unidentified post quality check |
|
QC Failed Reason |
The reason why a product has failed the QC |
|
ASN Created At |
The date the ASN was created at |
|
asn_schedule_date |
The date the ASN was scheduled at |
|
asn_completed_at |
The date the ASN was completed at |
Use Cases
- To find out how many units you have inbounded and noon received from a particular PSKU
- To find out how much units you have inbounded and noon received from a particular ASN
- To find out which products have had the most QC Fails for a particular time period
- To find out the total number of unidentified products over a particular time period
That’s it!
Got more questions?
Contact us at seller@noon.com
Related Articles
Accessing FBN Reports on Seller Lab
The FBN Reports in Seller Lab provide a centralized and streamlined solution for tracking and analyzing your Fulfilled by Noon (FBN) inventory. These reports cover everything from stock levels to returns and inbound processes, enabling better ...Reports & Analytics Comprehensive Overview
Understanding Your Sales About the Sales View: Start here to get a grasp of your sales overview. This article introduces you to the sales dashboard where you can access comprehensive sales views, filter sales data by item status, and get consolidated ...Fulfilled By Noon (FBN) Comprehensive Overview
This enhanced seller's guide through the FBN ecosystem is designed to equip sellers with the knowledge and tools they need for a successful e-commerce operation on Noon. By taking a deep dive into each aspect of the FBN service, from logistics and ...New Inventory Ledger Reports (Summary and Detailed View)
The Inventory Ledger Report is a vital tool for efficiently managing your FBN inventory. It offers a detailed overview of stock movements and transactions within Noon fulfillment centers, allowing you to monitor your inventory effectively. The report ...Managing your returns/ Managing FBN returns
noon gives the customers the option to return purchased items. Any order that has been shipped, falls within the returnable categories and is within the 15 days’ limit from the date of delivery, can be filed for return. All customer returned units ...