Skip to main content

Filter by idea status

Filter by product

2599 Ideas

Andy K.
Andy K.Employee

Serial# Change BehaviorUnder Review

I love that ShipStation has finally added the Serial# Feature in ShipStation, but I would love an update to the background logic by which this system works.First let me present the scenario we are running into. We have a variety of products. Some are fully custom and made to order, others are assemble to order, others are ready to ship. We have quite a few orders that are large multi parcel shipments with a variety of different products in them. These products will often come through production at wildly different times depending on our lead times for certain departments. In instances like this we like to pack the boxes as we receive items as it is far more efficient from a floor space perspective. We would love to use the serial number feature during this this process but are running into some issues with the way the logic currently works. Right now if we use scan to verify and enter a serial number the serial number saves but the verified status does not. A large dealer order might consist of twenty to thirty of the same item all requiring serial numbers which means we are reverifying items that have already been scanned every time we scan a new item with the same SKU. Since a good number of these items have the serial number directly on the product we have to wait to receive all the product for a single SKU before packaging or manually reverify already verified serial numbers every time we receive another item. I would love if ShipStation could both save the serial number for a product and it’s verified status. So if I have fifty jackets of the same SKU going to a dealer and I scan jacket number fifty I don’t have to reverify the other forty nine jackets that I receive from production the day prior.

MaxDisctance
MaxDisctanceEmployee

Add an “Inventory Deduction Only” Mode for Product BundlesUnder Review

I would like ShipStation to add an option that allows bundle components to be used only for inventory calculations while the original imported product continues to function as a normal standalone product everywhere else. Current situation I sell completed products assembled from two shared inventory components. For example: XF10WH – XF10 White Disc Retriever - 1 × XF10 pole- 1 × white suction-cup ball The customer purchases "XF10WH" as one finished product for $54.99. I configured it as a Product Bundle because I need the sale to deduct one XF10 pole and one white ball from their respective inventory counts. Inventory deduction is the only bundle behavior I need. Currently, ShipStation replaces the original purchased product with its components throughout order processing. This creates several problems: 1. Order quantities become confusing.   An order containing 13 finished retrievers appears as 26 component units: 13 poles and 13 balls. 2. Splitting large shipments becomes difficult.   Employees must move the pole and ball components separately instead of moving the original finished product and quantity. 3. The original SKU and product name disappear from important screens.   Employees see the internal components instead of the product the customer actually purchased. 4. International customs declarations use the components instead of the imported product.   ShipStation recently transmitted the two components of a $54.99 retriever with $0 declared values. UPS placed the shipment on hold because the commercial invoice did not contain a valid customs value. 5. Fixed component customs values do not solve the problem.   The same components are sold individually and included in finished products with different prices. For example:      - XF10 White retriever: $54.99   - XF10 Black retriever: $64.99   - XF10 Glow retriever: $64.99   - White ball sold individually: $19.99   - Black ball sold individually: $24.99   - Glow ball sold individually: $27.99      A fixed customs value assigned to each component cannot always reproduce the actual transaction value of the finished product. Requested feature Please add a bundle setting called something similar to: Use components for inventory calculations only When enabled, ShipStation should: - Deduct and commit inventory from the bundle components.- Calculate bundle availability from component inventory.- Preserve the original imported SKU, product name, quantity and selling price in Order Details.- Treat the original bundle as one product in the Split Shipment screen.- Use the original imported product and transaction value for customs declarations and commercial invoices.- Preserve the original product in reports, exports and other order-processing screens.- Allow users to expand the bundle when they need to view its components. The product should otherwise behave exactly as it would if it were a standalone product. ShipStation already offers a “Show bundle only” option for packing slips. I am requesting comparable behavior throughout Order Details, shipment splitting, customs documents and the rest of the fulfillment workflow, while component inventory deductions continue in the background. ShipStation Support has confirmed that this workflow is not currently available. Adding it would make Product Bundles much more useful for businesses that assemble finished products from shared inventory components without treating those components as separate customer-facing products.

jennifer12
jennifer12Employee

Full Amazon Buy Shipping Compatibility for Multi-Warehouse / Multi-Carrier SetupsUnder Review

ShipStation should fully support Amazon Buy Shipping configurations where different Amazon warehouse / Ship From locations are tied to different carrier accounts within the seller’s Amazon account.In our case, we use multiple UPS accounts with different negotiated rates. Amazon exposes those through different warehouse / Ship From configurations, so the available Buy Shipping rates can vary depending on which warehouse is used.Amazon’s Shipping API supports multi-warehouse rating through the applicable registered shipFrom location. ShipStation should be able to request rates for each eligible Amazon Ship From location, return the carrier options associated with that location, and feed those results into Rate Shopper.That would allow ShipStation to:Compare Amazon Buy Shipping rates across eligible Ship From locations Include the carrier accounts tied to those locations Select the cheapest valid option that still meets Amazon’s delivery promise Purchase the label through Amazon Buy Shipping using the selected rateThis is important for more than just convenience.Without this functionality, we lose money on shipping because we cannot fully use all of the carrier accounts available within Amazon while still maintaining the protections tied to Amazon Buy Shipping and OTDR. We can end up selecting a more expensive rate under the default warehouse even though a cheaper valid option should be available through another warehouse/carrier-account configuration.We have also consistently seen technical instability in ShipStation’s Amazon Buy Shipping integration when multiple carrier accounts are connected in Amazon. We encounter internal errors, failed rating behavior, and in some cases issues severe enough to effectively break the integration.That makes this feel less like an enhancement request and more like a compatibility gap that needs to be fully addressed.If ShipStation advertises Amazon Buy Shipping as a supported carrier integration, it should fully support the configurations Amazon sellers are allowed to use within Amazon Buy Shipping.A seller should not have to simplify or remove legitimate carrier-account configurations just to keep the ShipStation integration stable.For sellers relying on Amazon Buy Shipping protections, OTDR, and negotiated carrier rates, incomplete support creates real shipping-cost, workflow, and account-health consequences.