short description of an order status

Subject: short description of an order status
From: Elise Kaplan <EKaplan -at- micros-retail -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 26 Feb 2010 09:35:21 -0500

We're trying to come up with a short description of a status to assign to orders in an integration between a direct fulfillment center and a retail outlet. In this scenario, the direct fulfillment center ships the merchandise to the retail store, where the customer picks it up. When the customer has picked up the order, the status will be Complete. The scenario that we're stuck on is when the customer has picked up some of the items on the order, but not all. For example, the customer shows up at the store and picks up a few smaller items, but then realizes that his new wide-screen TV won't fit in his car, so he says that he will return when he borrows his brother's van.

The status needs to be short: 15 positions or fewer, including spaces. Also, it needs to be clearly different from the other possible statuses throughout the whole order process, which number approximately a kajillion. Some of our thoughts:

- Partial pickup

- Incomplete

- Unfinished

We also need a one-letter code to indicate the status in database tables and on certain screens. Unfortunately, the letters P, A, R, I, and U are already taken. Also, we already have an "In process" status, which indicates a completely different phase in the order process.

The best I can come up with is "Partial Pickup" and the one-letter code of T. I think that "incomplete" and "unfinished" are a drag, with negative connotations. But the rest of the team is underwhelmed by my suggestion. Thoughts?

Elise Kaplan I Documentation Manager I MICROS-Retail (Datavantage, CommercialWare, eOne Group) I 1800 West Park Drive I Westboro, MA 01581 I
508.652.9487 * I 508.647.9495 * I ekaplan -at- micros-retail -dot- com<mailto:ekaplan -at- micros-retail -dot- com> * I<>

Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


Previous by Author: Re: Naming a department
Next by Author: RE: Need a word for...
Previous by Thread: RE: RE: my bad displays habit
Next by Thread: RE: short description of an order status

What this post helpful? Share it with friends and colleagues:

Sponsored Ads