> For the complete documentation index, see [llms.txt](https://docs.p4.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p4.software/p4warehouse-english/setup/system-configuration/fulfillment/data-entry.md).

# Data Entry

On this screen you will configure the Data Entry defaults.

![P4 Warehouse Data Entry Configuration](/files/-Mj4KlSreM1iZr8brkZ7)

1. Pick Ticket Number Prefix - This is the prefix that will display in front of your sales order numbers. (PCK-0001)
2. Warehouse Transfer Number Prefix - This is the prefix that will display in front of your Transfer order numbers. (TRNS-0001)
3. Default Freight Type - This will be the default freight type. If you mostly ship FedEx or UPS here you would select Small Parcel. This is the default however at the order level you can select the correct shipping method.
4. Default Count on Ship - This is to require a recount of the product prior to completing the shipping process.
5. Default Sign on Ship - This will cause the order to require a signature on shipping and allow a photo to be captured of the product prior to shipping.
6. Default Count on delivery - This will require the delivery driver to recount each pallet or box on delivery.
7. Default Sign on Delivery - This will require the delivery driver to require a customer signature on delivery. Also, a photo can be captured in the delivery process.
8. Packsize Entry type is Packs or eaches, this determines the default label to print depending on the type of warehouse you operate.
9. Duplicate Sku Value - This determines if duplicate sku's re allowed on an order. This is often set to "Prevent" to reduce the chance of double data entry. This is extremely useful when keying large orders.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.p4.software/p4warehouse-english/setup/system-configuration/fulfillment/data-entry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.