Don’t believe the conventional wisdom; Parcel is not a “black box” that you setup and never have to touch again.  Like any complex software, it will need attention.

Regrettably, most Parcel implementations fall victim to this mentality and perform-ance issues arise.  The steps to avoid this are not difficult, but easy to overlook.

When your implementation begins to slow down this indicates excessive data is lurking under the surface and no maintenance is being performed to keep it trim.


While it makes sense to archive most historic transactional data when working with the JDA warehouse management system, Parcel is unique.

The data that Parcel amasses can be categorized into two buckets:

  1. Transactional – granular data used to enforce carrier rules
  2. Structured output – tracking numbers, shipping charges, and high level details

Most carriers invoice on a weekly basis which means keeping more than four weeks of transactional data in Parcel is unnecessary.  With that said, archiving this type of data does not add value; it’s an avoidable operating cost.  We like those too.

On the same front, the structured output is shared with the WMS.  Once shared, the WMS will archive all of its shipping related data, including the Parcel data.


We typically recommend purging Parcel data roughly 30 days after it has been used and transmitted to the relevant carrier.  The data has served its purpose by this point.

In order to purge the transactional data, we need to understand a Parcel concept called a manifest.  It is a collection of packages created during a specific period of time and for a single carrier.  Luckily, functionality exists to purge manifests.

Parcel, like the WMS, includes the ability to schedule jobs and you would need to define a new job tasked with finding manifests that were closed 30 or more days in the past and leverage the purge command to remove them.


When shipping to consumers, you inevitably end up with addresses that are used once or infrequently at best.  These addresses build up over time and Parcel has no baked in way of removing them.  A custom purging solution is needed as excessive address data negatively impacts performance within Parcel.

Beyond the technical aspects of the implementation, Parcel requires a substantial amount of carrier specific knowledge to ensure success.  This is hard earned expertise and experience.  If you’re questioning whether you are on solid footing, it’s best to reach out to seasoned professionals.