> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/pakk-services/fulfilled-by-pakk-fbp/the-fbp-tab.md). # The FBP Tab The FBP tab appears on Locations and Shipping Methods, but in these cases they are just there for the initial configuration. The real functionality is on Products, Sales Orders, and Purchase Orders. For those entities, you will see: * "*Send/Update to FBP*" and "*Sync from FBP*" buttons. The Send/Update buttons send information from Pakk to the FBP subsystem, and the Sync button retrieves information from the FBP subsystem. * "*On FBP tick box*": Indicates whether this record has been successfully sent to the FBP subsystem. This is a status field and cannot be edited manually. * "*FBP Identifier*": The internal ID for this record on the FBP subsystem. * "*Created on FBP*": The timestamp when this record was created on the FBP subsystem. -" *Last Synced from FBP*": The timestamp when this record was last synced from the FBP subsystem. 'Sync' means pulling updates from FBP into Pakk. * "*Last FBP Error*": The most recent error (if any) when communicating with the FBP subsystem. These fields are generic and replicated across the relevant list views, but there are additional fields relevant to each specific entity. Let's go through them. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pakk.io/pakk-services/fulfilled-by-pakk-fbp/the-fbp-tab.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.