{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":48798,"path":"servicenow-platform/service-catalog/c_FlexibleCheckoutAndDeliveryForms.md","title":"Legacy flexible checkout and delivery forms","bundle":null,"doc_type":null,"release":"australia","body":"\n# Legacy flexible checkout and delivery forms\n\nServiceNow includes several options that provide administrators some control over content in service catalog template-driven forms.\n\nSome service catalog forms, such as the checkout form, are generated from templates, instead of being data-driven like other forms in the system, such as the Incident form.\n\nTemplate-driven forms provide enhanced look-and-feel over standard data-driven forms, but they provide more limited control over the form content.\n\n**Note:**\n\nIt is recommended that you use cart layout records to configure cart layouts. Using cart layout records lets you configure the service catalog cart without writing and maintaining scripts.\n\n-   **[Modifications in the delivery screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-catalog/c_ModifyTheDeliveryScreen.md)**  \nIn the final checkout step, a summary screen provides a list of all items and services ordered.\n-   **[Modifications in the checkout form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-catalog/c_ModifyTheCheckoutForm.md)**  \nYou can modify the checkout form to use an alternate description field or to add request item number for each line.\n\n**Parent Topic:**[Cart layout](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-catalog/c_ConfigureCartLayout.md)\n\n"}}