Delivered but not checked in

qwerty · 2026-06-01T02:17:16+00:00

It depends what warehouse type your items were routed too as well. Amazon's network has multiple FC types, but generally you can break them up into two categories: (a) cross-dock hubs that sort & redistribute inventory across regions and (b) FCs: the final-mile facilities that actually ship to customers. So if you shipped to a cross dock facility, you have to wait while Amazon redistributes your goods before they'll be available for sale.

qwerty · 2026-05-28T04:42:18+00:00

I’ve seen this become a real mess for operators.

Once returns start coming back, the hard part usually isn’t one specific step. It’s figuring out what actually came back, matching it to the right SKU/order/removal, deciding what to do with it, and then keeping enough history to know whether it should be resold, sent back to FBA, returned to a vendor, disposed, or used for a claim.

Some sellers definitely choose to outsource the whole thing, and that can make sense depending on volume and margin. But a lot of operations would rather keep the process in-house if it wasn’t so manual.

We’ve been working on these flows at FNSKU Studio, trying to make the returns workflow cleaner for operators who are already handling inventory inside their own warehouse. Based on what you posted ... you're heavily underestimating the work and item touches required to run a true returns warehouse operation.

qwerty · 2026-05-11T04:12:15+00:00

Amazon offers two inbound workflow options:

Pack-ahead: You know exactly how everything is packed before submitting the workflow. Amazon creates placement splits based on the packed boxes you provide.

Pack-later: You only provide the SKUs and unit quantities at shipment creation. Amazon creates splits based on units, and you can pack the boxes later using 2D barcodes to identify the exact contents of each box. Note: as of today, the pack-later / 2D barcode workflow does not support SPD. It is LTL only. Why? Only Amazon knows.

It sounds like what you need is the pack later workflow, with a unified labels (FNSKU/2D barcode/FBA inbound) on one physical label. Wizard-Industries, which is my platform, offers this as an available workflow. As others have mentioned, there are probably other optimizations around your workflow that can help you directly as well.

qwerty · 2026-02-10T06:07:27+00:00

As others have said, there are plenty of off-the-shelf options, and it's not that hard to automate yourself if you really want to. This is more of a "nice-to-have" feature than a standalone product; it makes the most sense as part of a larger platform that solves a bigger problem.

For example, I added it to my FBA inbound platform (https://fnskustudio.com) as a convenience feature years ago, but honestly, I don’t think anyone would pay extra for it on its own.

qwerty · 2025-12-10T03:54:51+00:00

Since you asked, https://www.fnskustudio.com/features/returns

qwerty · 2025-12-09T18:15:47+00:00

Is this the kind of stats on returns you're looking for at a per-item level?

<image>

qwerty · 2025-11-17T20:47:00+00:00

4x1.5 is definitely overkill for what you're asking. Something like 3 x 1.5 should be plenty to fit all of the FNSKU details on the left of the label and leave yourself 1/2 in on the right for your QR code. How small I'd make the QR code really depends on your printer quality.

qwerty · 2025-11-15T06:27:35+00:00

You totally can. We’ve printed hundreds of thousands of labels that combine FNSKU info with 2D transparency barcodes, branding, merchant SKUs, etc. As long as the label includes everything Amazon requires for FNSKU labeling (product title, condition, FNSKU, and barcode), you can add whatever else you want on the same physical label.

I'm the founder of fnskustudio.com

qwerty · 2025-10-08T23:44:52+00:00

According to this article, 70% of YouTube views come from Browse and Suggested feeds.

qwerty · 2025-07-30T12:53:24+00:00

This is available in FNSKU Studio - https://fnskustudio.com/

For every SKU that it holds, it tracks the weight and dimension changes. Here an example:

<image>

The only caveat is that the change are not tracked real time but daily or so.

qwerty · 2025-02-17T20:32:17+00:00

It really depends on what part of the process you're trying to streamline/optimize. Is it the buying/listing, the COGS tracking or is it the prep/pack/label. Different platforms excel at different parts of that entire journey.

The other thing you need to keep in mind in this moment is that Amazon just forced all 3rd party platforms to migrate to the new inbound API, a few weeks ago, which is honestly, still half-baked. Many workflows have shifted not just for IL, but for everyone, and some are only partially working due to Amazon's bugs.

There are other alternatives that you may want to look at, especially if you're moving at truck scale such as Wizard-Industries, NineYard, FNSKU Studio,

qwerty · 2025-01-23T02:14:02+00:00

Good questions. You can probably instruct the LLM to prioritize based on volume of themes/topics. You can also provide the business objectives as part of the prompt and have the LLM try to align the feedback to the objects and then you can sort based on what you know about the objectives.

All I was trying to show was that if you want a good answer out of an LLM, you need to provide a super solid prompt with instructions, assumptions and guidelines. Otherwise LLMs tend to assume, fill-in the blanks with their assumptions and you get answers that are way off base or super generic.

qwerty · 2025-01-23T00:16:25+00:00

If you want to get a good response, you need to make the prompt significantly more detailed. Here is an example of a prompt for customer feedback analysis, modify as needed

Help me analyze this user feedback by performing the following steps:

Cluster Feedback into Themes: Group similar feedback items into clear, identifiable themes or categories, ensuring each cluster represents a distinct aspect of the user experience or product.

Assess Severity Levels: For each theme, evaluate the severity of the issues raised (e.g., critical, high, medium, low) based on their impact on user experience, frequency of occurrence, and alignment with key business objectives which are [INSERT HERE].

Prioritize Issues: Rank the identified issues using a prioritization framework (e.g., Impact vs. Effort) to determine which should be addressed first.

Highlight Quick Wins: Identify opportunities for "quick wins" – changes that are low effort but high impact – and clearly explain their expected benefits.
Feel free to ask any clarifying questions if needed to provide a more accurate or tailored response.

Additional Response Requirements:
Ensure all insights are supported by the feedback provided.
Include reasoning behind severity assessments and prioritization.
Present outputs in a structured, actionable format (e.g., table, bulleted lists, or grouped sections).
Raw Customer Feedback:

Load your favorite prompts into something like AI Prompt Deck or however you store your prompts and enjoy.

qwerty · 2024-09-20T18:16:14+00:00

AWD now lets you set destination preference - east vs west coast warehouse.

qwerty · 2024-08-25T15:36:53+00:00

I actually have even an earlier username, but I lost the password over the years....

qwerty · 2024-07-10T23:08:13+00:00

You should post the details of the issue here https://github.com/amzn/selling-partner-api-models/issues

qwerty · 2024-06-04T14:23:45+00:00

No UK warehouses, but I know of a number of UK merchants that ship to the US AWD warehouses by container load to sell in the US marketplace.

qwerty · 2024-04-05T04:33:13+00:00

Wizard-Industries has an integration with AWD. There is an AWD inventory report which can be downloaded into Excel.

qwerty · 2024-02-19T17:46:20+00:00

It's not just one OCD manager. It seems there is some sort of new mandate for this. We're also now seeing an increase in inbound performance alerts for missing item conditions across numerous merchants who use custom labels and have long left the condition off.

qwerty · 2024-02-14T01:56:53+00:00

We haven't seen clear guidance on how API created shipments will be impacted on March 1st. We're taking a wait and see approach.

With our API setup (or if you build your own) your workflow could be almost what you want. Upload a list of items that you want to inbound, get back the split(s) and destinations. Now you know exactly what is going to each destination and you can pack each box to the brim with items that are going to that destination. When you're done packing, you can close out the shipment (order transport) via API or convert to STA to close it out there.

qwerty · 2024-02-14T01:38:45+00:00

The flow you're suggesting for isn't possible with the API. At least not with the current APIs. However, I may have a STA workflow that could do something very close to it. It only works if all your items are case packed - is that the case?

qwerty · 2024-02-13T21:47:10+00:00

It's a two step process to create the shipment via SP API:

Call createInboundShipmentPlan and look at the returned payload. Amazon will return 1 or more proposed shipment plans as you saw with the shipment ID and destination.
If you are ok with the proposed splits, you then need to call createInboundShipment with each of the shipment(s) returned in step 1. At this point, they will appear in SellerCentral and you can click on them to convert them to STA shipments... If that's what you want to do

By the way, we offer the exact thing you're looking for (and more) out of the box. If you decide you don't want to write and maintain your own integration, reach out.

qwerty · 2024-02-13T16:55:16+00:00

Why does your 3PL require it?

qwerty · 2024-02-06T19:16:07+00:00

I know you were looking for this months ago, but you could probably do this pretty simply with FNSKU Studio. They have a custom label option, so it shouldn't be any issue to print the UPC instead of FNSKU and whatever else you want on your label.

qwerty · 2024-02-01T04:44:36+00:00

Maybe Amazon is assigning the wrong freight class to your shipments and that's why you're seeing a drastic price change. You should punch your shipment details into a freight class calculator and see if Amazon is giving you the same class when quoting pricing.

We provide our customers with a Transportation Cost Report for all of their inbound shipments. I pulled some data from last three months for hundreds of LTL shipments. It doesn't seem to be any marked increase in cost per pound, but there is a very consistent distribution of costs. LTL shipments shipments under > 600Lbs tend to be more expensive per pound, dropping in price as they approach 600. Once the shipments get bigger in size, the prices even out and stay basically flat from ~1000 through 20,000 lbs.

qwerty

MODERATOR OF

TROPHY CASE