Conversations and Delivery
Once requirements are submitted, the buyer and seller communicate through a conversation thread on the single order screen. This is where messages, file attachments, the final delivery, and the accept or reject decision all happen.
The conversation thread
Section titled “The conversation thread”Each message is stored in the wp_edd_sell_message table and rendered as a chat, with the current user’s messages aligned to one side and the other party’s to the other. A message records the author, the buyer, the order (purchase) id, the product id, the message body, a timestamp, any attachments, and an “extra” payload used for delivery flags. The thread can also refresh through an AJAX endpoint (conversation_update) so new messages appear without a full reload.
Attachments
Section titled “Attachments”Both a message and a requirement answer can carry uploaded files. Message attachments are stored as URLs against the message row. Requirement and delivery files are served through a tokenized download link (the requirementsfile and token query parameters) rather than exposed directly, so the file name and path are obfuscated.
Sending a final delivery
Section titled “Sending a final delivery”The seller marks a message as the final delivery. This records the delivering message id on the order meta (edd_final_delivery_<paymentid>_<productid>) and moves the order to Waiting For Approval. The buyer sees a “Here’s Your Final Delivery” panel showing how many days the delivery took from the order start date.
Accepting or rejecting
Section titled “Accepting or rejecting”- Accept. The order moves to Waiting For Review, the payment is published and completed, and an acceptance record is stored (
edd_accept_delivery_<paymentid>_<productid>). If the buyer accepts without typing a message, the message defaults to “Order accepted”. - Reject. The recorded final delivery is cleared and the order returns to Work In Progress for redelivery.
Delivery date
Section titled “Delivery date”The seller can set or update a delivery date on the order through an AJAX action; the chosen date is stored on the order meta edd-update-delivery-date.
Recurring orders
Section titled “Recurring orders”For orders created through EDD Recurring or Subscriptions, the single order screen shows Previous Recurring Order and Next Recurring Order links so a seller can move between the payments in a subscription.