Interested in a shipping solution ideal for batch and automated shipping? The ShipRush Non-Visual Component is your answer. Since it is code-driven from the 'host' application, this component allows you to rate and ship without ever showing the ShipRush UI. Shipping is easy and completely integrated into your application.
- Developers working in Java, .NET, C++, Delphi and other tools
- In-house, contract and commercial developers
- Software in the WMS, order management, ecommerce and fulfillment segments
- Process rating and label transactions without showing the ShipRush GUI
- Generate large numbers of shipping labels (in bulk or batch)
- Calculate shipping costs
- Check shipping service availability
The Non-Visual Component is identical to the Visual Component in terms of its functionality making it easy for developers to get started with the Visual Component, and then migrate to the Non-Visual Component downstream.
The difference between Visual and Non-Visual Components is that with the Non-Visual Component, shipping and rating is done without showing the interactive ShipRush UI to the user. This means that ShipRush will process the shipment, but all required shipment parameters must be set from the host application in order for the shipment to proceed. Compared to the Web Service, the Non-Visual Component runs in-process, whereas the ShipRush Web Service runs outside your process. The Web Service never shows a ShipRush UI during shipping.
The Non-Visual Component offers programatic access to essentially the entire ShipRush system, providing for full shipping integration into your application.
The Non-Visual Component is perfect if:
- You want full control of the shipping UI and do not want to surface the ShipRush UI
- You run batches of shipments
- You are in an automated environment, without a computer operator present to use a shipping UI
Click here for a matrix comparing the different developer tools
For purchasing information click here.
Q: What is ShipRush?
A: ShipRush is an easy and efficient way to ship via FedEx, UPS, or USPS. ShipRush automatically pulls the 'Ship To' address into the shipping form. Enter a weight, press ship for your shipping label to print out and an automatic email to be sent to the customer with the tracking number.
Q: What is the ShipRush SDK?
A: The ShipRush SDK allows you to customize the benefits of "end-user ShipRush" to integrate within your own application. The ShipRush SDK is a suite of several developer tool sets that allow ShipRush to be used from within your application. With the ShipRush SDK you are able to use the same ShipRush technology we use in the end user ShipRush to ease the process of calculating shipping costs, creating shipping labels, and keeping accurate records of all the shipments you process.
Q: Why Shouldn't I just code to the shipping carrier myself?
A:If you choose a ShipRush developer tool, we do the heavy lifting. We are constantly updating ShipRush to stay current with the shipping carriers. And we know shipping front-to-back, because that is all we do. By using ShipRush we will take care of the constant updates and complex business rules of shipping that are critical to maintain your integration. You'll be able to ship worry-free.
Q: Can the non-visual tool handle batch shipping?
A: Yes! The non-visual tool is perfect for small or large batches.
Q: Are there any times my users would need to see the ShipRush UI?
A: The only required use of the ShipRush UI is for initial setup. However, a benefit of the ShipRush SDK is that you can optionally use the ShipRush GUI for features you don't want to embed in your application. For example, label reprinting or shipment voiding could be left to the ShipRush GUI, saving you a bit of integration effort.
Q: What's the difference between using the non-visual component and the Web Service tool?
A: The Web Service entry point is "over the network." This means that a single installation of the ShipRush Web Service serves your software on any and all PC's on the local network. A benefit of the component is that it is directly integrated into your application, and it is easy to switch (in your code) between the visual and the non-visual components. Unlike the Web Service, the non-visual component requires that ShipRush to be installed on all the PCs that will use the non visual component.
Q: What developer tools are most compatible with the ShipRush non-visual component?
A: Visual Studio.NET and Visual Studio v6, C++, Visual Basic, Microsoft Access and FoxPro, Delphi, and others.