The status record is part of the Petals XML based order and message
exchange service. It was introduced as part of Version 45 and will
not work with earlier versions. (see version history).
The status record is designed to echo-back information between
parties using the XML system. Its use is optional and partners will
need to advise Petals of the URL and password etc to use for Petals
to be able to send a status record to that party. This will normally
be the same used by Petals to send XML based orders and messages
to participating parties.
Evolution
- the original version of the status record was created in
March 2009 for beta usage
Current Fields
| Required |
Field Name |
Description |
Length |
Type |
| Y |
recordtype |
"02" = status record |
2 |
Character |
| Y |
member |
A Partner number for the Partner, issued by Petals |
5 |
Number |
| Y |
petalsid |
The Petals order reference number in the format mmmm.oooooo
made up of 3-5 Petals member number and 6 digit transaction
number supplied by Partner else set by Petals. |
15 |
Number |
| N |
sellid |
An optional order reference supplied by the seller of
the order to key into their system. Petals will try to pass
this number around the partners to make it more convenient
for the seller to find a referenced order in their system |
15 |
alpha/num |
| N |
supplyid |
An optional order reference supplied by the supplier
of the order to key into their system. Petals will try to
pass this number around the partners to make it more convenient
for the supplier to find a referenced order in their system |
15 |
alpha/num |
| Y |
password |
The password given to you by Petals. |
8 |
Characters |
| Y |
type |
A fixed code number for the information conveyed by
this status record. See the current list below. |
3 |
Character |
| N |
text |
Optional text message. There is no guarantee the recipient
will read or parse this message into their system. The 'type'
field should convey the specific issue. |
100 |
Character |
| N |
gmt |
Inserted by Petals: This contains a GMT datestamp in
XML format for when the status flag was sent by Petals.
The format is "yyyy-mm-ddThh:mm:ss" in 24hour time. This
may be of most use where incoming status messages are printed
or held in a store and might otherwise loose the time information.
GMT will be of most use when adjusting the time to your
local time zone using an offset against GMT. |
19 |
datetime |
| N |
petalsdt |
Inserted by Petals: Same as GMT except it is the local
Petals time. Mostly this will be helpful for Australian
Partners. |
19 |
datetime |
| N |
deldate |
Inserted by Petals: - delivery date yyyymmdd |
8 |
date |
| N |
recipient |
Inserted by Petals: - Name of person receiving flowers |
60 |
Character |
Error Code List
Current
| Code |
Meaning |
| 100 |
order received OK |
| 101 |
The delivery date incorrectly contains / symbol. Should
be yyyymmdd format (order
will NOT be processed) |
| 102 |
The delivery date has passed or is too close (order
will NOT be processed) |
| 103 |
Either we already have an order from you with this order
number or the order number data field is empty. Consequently,
we have NOT accepted this order (order
will NOT be processed) |
| 104 |
The Supplying Member number you gave appears invalid (order
will NOT be processed)
|
| 105 |
Data supplied for a field exceeds the maximum permitted
length. The data is truncated to fit the field. It is the
seller's responsibility to manage the data supplied. Order IS processed but with truncated data. |
| 300 |
message received OK |
| 301 |
This order number can't be found. Message is NOT forwarded |
| 302 |
The was no message in the XML. Message is NOT forwarded |
| 303 |
This message refers to an order that does not involve you. Order number is probably wrong. Message is NOT forwarded |
Future
| Code |
Meaning |
|
order rejected (under value, bad address, etc |
|
delivered to recipient |
Notes
- All field names and XML tags are in lower case, this is
to accommodate those systems that are case sensitive
- missing required data may cause the order to be rejected
by Petals. We will try to provide feedback on problems of this
type via email or web (and later with an XML record). However,
if we can't identify who the order is from, this will not be
possible.
- Petals presently shows a website response when it receives
an order and a confirmation email to the address supplied. There
are also periodic daily reconciliations emailed to all parties
for further checking.
- If any data field contains more characters than permitted
in that field, it will be truncated at the maximum field size
automatically (and possibly without notice). It is the responsibility
of the order sender to 'pack' their information fields to fit
within the maximum field size.
