Configure POS fulfillment types and payment methods
On this page
You can control which fulfillment types and payment methods are available to POS staff, and customize how they are labelled in the interface. Both are configured using store variables on the Store record in Salesforce.
For general information on adding store variables, see Store variables.
Configure fulfillment types
POS supports the following fulfillment types out of the box:
| Fulfillment type | Default label |
|---|---|
takeaway |
Takeaway |
delivery |
Delivery |
pickup |
Click & Collect |
hold |
Hold |
transfer |
Transfer |
reserved |
Reserved |
special_order |
Special order |
Enable or disable a fulfillment type
To hide a fulfillment type from the POS fulfillment picker, add a store variable with:
- Key:
pos.fulfillment_types.{type}.enabled - Value:
false
Replace {type} with the fulfillment type key from the table above.
Example: To remove the Hold option from POS, add a store variable with key pos.fulfillment_types.hold.enabled and value false.
:::note Delivery fulfillment also requires shipping to be enabled on the store and at least one shipping rate or provider configured. Disabling delivery here hides the option from staff even when shipping is otherwise configured. :::
When a fulfillment type is disabled, it is also removed from the fulfillment options shown on cart items — not just from the fulfillment picker. If all fulfillment types are disabled, the fulfillment section on cart items is hidden entirely.
Customize fulfillment type labels
If your business uses different terminology — for example, “Shipping” instead of “Delivery” — you can override the default labels using store variables.
Three label attributes can be customized per fulfillment type:
| Attribute | Key pattern | Effect |
|---|---|---|
| Singular label | pos.fulfillment_types.{type}.label |
Name shown in the fulfillment picker and throughout the POS |
| Plural label | pos.fulfillment_types.{type}.pluralized_label |
Plural form used in summaries and counts |
| Action label | pos.fulfillment_types.{type}.action_label |
Verb shown on the arrange fulfillment button |
Example: To rename Delivery to Shipping throughout the POS:
| Key | Value |
|---|---|
pos.fulfillment_types.delivery.label |
Shipping |
pos.fulfillment_types.delivery.pluralized_label |
shipments |
pos.fulfillment_types.delivery.action_label |
Arrange shipping |
You can set any combination of these — you do not need to set all three for a label override to take effect.
Configure payment methods
Enable or disable a payment method
To hide a payment method from the POS checkout, add a store variable with:
- Key:
pos.payment_options.{type}.enabled - Value:
false
Supported payment type keys:
| Type key | Default label |
|---|---|
cash |
Cash |
card |
Card (manual) |
card_integrated |
Card (integrated) |
cheque |
Cheque |
bank |
Bank transfer |
voucher |
Voucher |
on_account |
Pay on account |
account_credit |
Account credit |
Example: To remove the cheque/check option, add a store variable with key pos.payment_options.cheque.enabled and value false.
:::note Disabling a payment method hides it from POS staff at checkout and also prevents it from appearing as a refund option. It does not affect payment methods available on the web checkout. :::
Require a purchase order number
For payment methods used in B2B contexts (such as Pay on Account), you can require staff to enter a purchase order number before the payment can be accepted:
- Key:
pos.payment_options.{type}.require_purchase_order - Value:
true
When enabled, the POS prompts for a purchase order number at checkout for that payment method.
Customize payment method labels
To rename a payment method in the POS interface, add a store variable with:
- Key:
pos.payment_options.{type}.label - Value: The label text to display
Example: To display “Credit card” instead of “Card (manual)”:
| Key | Value |
|---|---|
pos.payment_options.card.label |
Credit card |
For broader payment method setup — including enabling integrated card devices — see Configure POS payment methods.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.