A watch company has good reason to dislike wasted time. When Joseph Cabrera sat down with two Movado executives in Las Vegas, the conversation concerned the unglamorous journey that follows a glamorous purchase: getting the thing into a box, onto the right service, and across the right border. Cabrera, seated beside the customer rather than alone on a stage, offered a useful introduction to his working world. The watch gets the admiring glance. Someone still has to arrange its departure.
Cabrera is the co-founder and CEO of ShipERP, the Long Beach shipping software business also represented in company announcements by his title of managing partner. His career puts him at the intersection of enterprise systems, carriers and customers with highly particular requirements. It is a place where the word “simple” tends to arrive after a considerable amount of work. His recurring concern is how to make that work fit the business already doing it.
The questions before the software
Movado needed wider geographic coverage, better handling of dimensional rating and connections to specific FedEx services. Cabrera described the preliminary work as a “mini blueprinting session”. Requirements came first; the relationship was being tested at the same time. For a buyer, the discovery process offered an early view of how this prospective partner would behave once the engagement became real.
His advice also reached beyond delivery. A support team should understand the customer's operation well enough to connect the dots when a call comes in. Having to explain the business afresh would consume time precisely when the customer needed help. “We pride ourselves on that.” It is a modest sentence, and a revealing choice of something to be proud of: institutional memory, available when needed.
A business inside the business system
In November 2010, ERP Integrated Solutions announced SAP NetWeaver certification for ShipERP version 1.0. Cabrera was identified as CEO. The product was an ABAP add-on for SAP ERP 6.0, designed to connect shipping activity with the system a company already used to run its business. Small parcels, less-than-truckload freight and truckload carriers all belonged within the scope.
Certification gave a concrete technical form to the proposition. Carrier selection, rate quotes, shipment creation and tracking could be handled through an integrated application. For Cabrera's company, this established a specific place in enterprise software: the connection between an internal business record and an external delivery network. An order could be perfectly respectable in the accounts and still require quite a lot of assistance to leave the building.
The attraction of that position is easy to understand. Businesses invest in systems to keep their operations coherent. Every additional handoff creates another point at which information must travel correctly. ShipERP's early architecture addressed that practical concern inside SAP. Cabrera's business was attached to a necessary transaction, repeated whenever a customer had something to send.
Business order→02
Carrier choice→03
Shipping label→04
Delivery tracking
The conference booth years
By 2013, Cabrera was discussing the company's work with UPS while ERP Integrated Solutions sponsored a SAPinsider conference. His description paired native shipping functionality with specialists who worked closely with customers. That pairing matters. Software could provide the machinery; people still needed to understand the business process it was supposed to serve.
The setting was suitably practical: an exhibition booth, demonstrations and conversations between conference sessions. It is a different kind of visibility from a consumer launch. The audience comes with existing systems and awkward questions. A successful conversation might involve a carrier service, an integration requirement or a process that has survived several previous attempts at improvement. There is limited room for theatrical mystery when someone wants to know whether a label will print.
The next product milestones followed that same route to customers. ShipERP 2.0 was announced for the 2014 SAPPHIRE NOW and ASUG conference in Orlando. The company described connections to more than 200 carriers worldwide. Its list of functions ran from address validation and compliance documentation to proof of delivery. These are small pieces of an operation until one goes missing.
In 2015, version 3.0 again appeared on the conference agenda. Cabrera described integration with both SAP ERP and SAP Extended Warehouse Management. The product's territory now explicitly included the warehouse application as well as the enterprise system. His public appearances chart a business advancing through releases, integrations and customer conversations, with the same basic shipping problem waiting at each new address.
“We are ShipERP!”
Joe Cabrera, announcing the company identity on LinkedIn
When the product became the name
On February 21, 2020, ERP Integrated Solutions announced that it would trade as ShipERP. The flagship product supplied the company name. Cabrera explained the change in terms of making the identity reflect the value delivered to customers. A long corporate description gave way to a shorter indication of the work.
There is a pleasing economy to that choice. Enterprise software names often require a second sentence and, occasionally, a small diagram. ShipERP places shipping next to the business system in seven characters. The rename also made the product's importance to the company explicit. What had been one name within the business became the name on the business.
The announcement coupled the change with continued customer relationships and a dedicated support operation available around the clock. The emphasis returned to service after purchase. For Cabrera, the public explanation of a new identity included the decidedly familiar obligation to answer customers. A new sign on the door still leaves someone responsible for the telephone.
For a business selling integration, the naming decision made the connection unusually legible. Customers could recognise the product they used in the identity of the people supporting it. Cabrera’s brief LinkedIn announcement suited the occasion: a straightforward introduction to a company whose work was already familiar to its customers. The product and the organisation would now answer to the same name.
The order has a neighbour
A partnership with DataXstream in June 2022 extended the conversation toward order management. DataXstream's OMS+ handled sales and order processing within SAP; ShipERP brought shipping and compliance expertise. The two businesses addressed adjoining parts of the same commercial activity. A customer placing an order and a warehouse sending it were connected events, even when software procurement treated them as separate subjects.
Cabrera's enthusiasm centred on integration that could remain easy to use despite its sophistication. That ambition is consistent with the business he had been describing for years: preserve the useful complexity behind the process while making the process manageable for the person carrying it out. The partnership widened the range of work that could be considered together.
It also shows why partner relations belong alongside business operations in his role. A shipping application depends on connections: to enterprise software, to carriers and to neighbouring applications. Building those relationships is part of building the product's usefulness. The customer encounters the result as a working process, rather than a collection of introductions.
Beyond the SAP address book
At Oracle CloudWorld in September 2024, Cabrera appeared with Kevin Luckenbach of Herber Aircraft Service. Their subject was integrating ShipERP with Oracle Fusion. The familiar shipping problem had crossed into another enterprise environment. Cabrera was again presenting alongside a customer, discussing a named operation rather than an imaginary ideal warehouse.
The significance is in the continuity. An enterprise platform may change, but the need to connect it with shipping remains. The conference appearance gave Cabrera's work a broader frame than the SAP roots that defined the earlier releases. His company's current emphasis on supporting different ERP platforms carries that same direction forward.
A founder in this position has to preserve specialist knowledge while making it useful in more places. Too little attention to the platform leaves an integration shallow. Too much attachment to one platform can limit where the business goes next. Cabrera's appearances across these two software communities make that balancing act visible without requiring a grand declaration about it.
The customer gets the last word
In 2025, ShipERP received a John Deere Supplier Innovation Award. The recognition concerned the company's work supporting the Parts IT Modernization initiative, particularly carrier and route determination. Team members accepted it at the John Deere Logistics Conference in June. This was a company award, with the work of a wider team behind it.
One detail brings the story back to Cabrera's earlier advice. ShipERP solutions architect Shekhar Saseendran described close collaboration with John Deere, including subject expertise during requirements finalization and technical support through the project. Requirements, partnership, follow-through: the practical concerns from the Movado conversation appear again in a different engagement, years later.
That repetition gives Cabrera's career its shape. Releases matter. Carrier connections matter. A company name can matter, too. But the work keeps returning to an operation specific enough to resist a generic answer. There is a certain satisfaction in a business whose claims eventually meet a shipping desk. The parcel is waiting. Someone must know what happens next.