{"id":1458,"date":"2026-03-25T14:52:35","date_gmt":"2026-03-25T14:52:35","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?p=1458"},"modified":"2026-03-30T06:12:49","modified_gmt":"2026-03-30T06:12:49","slug":"netsuite-wholesale-distribution","status":"publish","type":"post","link":"https:\/\/aaxonix.com\/resources\/netsuite-wholesale-distribution\/","title":{"rendered":"NetSuite for Wholesale Distributors: From Purchase Order to Customer Delivery"},"content":{"rendered":"<style>\n.aax-post{font-family:'Poppins',sans-serif;color:#1a2332;max-width:820px;margin:0 auto;line-height:1.75}\n.aax-post h2{font-size:1.55rem;font-weight:600;margin:2.5rem 0 .9rem;color:#0a1628}\n.aax-post h3{font-size:1.15rem;font-weight:600;margin:1.8rem 0 .6rem;color:#1a2332}\n.aax-post p{margin:0 0 1.1rem}\n.aax-post ul,.aax-post ol{margin:0 0 1.1rem;padding-left:1.5rem}\n.aax-post li{margin-bottom:.45rem}\n.aax-post table{width:100%;border-collapse:collapse;margin:1.5rem 0;font-size:.93rem}\n.aax-post th{background:#0a1628;color:#fff;padding:.6rem 1rem;text-align:left}\n.aax-post td{padding:.55rem 1rem;border-bottom:1px solid #e8edf4}\n.aax-post tr:nth-child(even) td{background:#f5f7fb}\n.aax-post .faq-section{background:#f5f7fb;border-radius:10px;padding:1.8rem 2rem;margin:2.5rem 0}\n.aax-post .faq-item{margin-bottom:1.2rem;border-bottom:1px solid #e0e6ef;padding-bottom:1.2rem}\n.aax-post .faq-item:last-child{border-bottom:none;margin-bottom:0;padding-bottom:0}\n.aax-post .faq-question{font-weight:600;color:#0a1628;margin-bottom:.5rem}\n.aax-post .faq-answer{color:#3a4a5c;line-height:1.65}\n<\/style>\n<div class=\"sp-toc-wrap\"><nav class=\"sp-blog-toc\" id=\"spBlogToc\" style=\"display:none\"><h4><svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\" width=\"18\" height=\"18\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" style=\"vertical-align:middle;margin-right:6px\"><line x1=\"8\" y1=\"6\" x2=\"21\" y2=\"6\"\/><line x1=\"8\" y1=\"12\" x2=\"21\" y2=\"12\"\/><line x1=\"8\" y1=\"18\" x2=\"21\" y2=\"18\"\/><line x1=\"3\" y1=\"6\" x2=\"3.01\" y2=\"6\"\/><line x1=\"3\" y1=\"12\" x2=\"3.01\" y2=\"12\"\/><line x1=\"3\" y1=\"18\" x2=\"3.01\" y2=\"18\"\/><\/svg>On this page<\/h4><ol class=\"sp-toc-list\" id=\"spTocList\"><\/ol><\/nav><\/div>\n<div class=\"aax-post\">\n\n<p>Wholesale distribution looks deceptively straightforward on paper: buy goods, store them, sell them, ship them. In practice, the operational picture involves hundreds of SKUs spread across multiple warehouses, vendor lead times that shift without notice, customer pricing agreements negotiated at the account level, and freight costs that need to land on item records before margins mean anything. Most general-purpose ERP systems handle one or two of these requirements adequately. <strong><a href=\"https:\/\/aaxonix.com\/products\/netsuite-erp\/\" class=\"sp-content-link\">NetSuite<\/a> wholesale distribution ERP<\/strong> was built to handle all of them in a single connected system. This guide walks through exactly how, covering inventory architecture, landed costs, purchasing, pricing, order fulfilment, and a side-by-side comparison against the two alternatives distributors most often evaluate.<\/p>\n\n<img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/wholesale-distribution-warehouse.jpg\" alt=\"Wholesale distribution warehouse logistics\" style=\"width:100%;border-radius:8px;margin:1.5rem 0\" loading=\"lazy\">\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/inline-netsuite-wholesale-distribution-1.jpg\" alt=\"netsuite wholesale distribution erp\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure><h2>The operational complexity of wholesale distribution and where generic ERP falls short<\/h2>\n\n<p>Wholesale distribution sits at the intersection of procurement complexity and fulfilment pressure. A distributor buying electrical components from six manufacturers, storing them across three regional warehouses, and selling to 200 contractors under individually negotiated pricing schedules is managing a web of dependencies that generic ERP handles poorly.<\/p>\n\n<p>The most common failure points in non-specialised systems are:<\/p>\n\n<ul>\n  <li><strong>Inventory visibility:<\/strong> Stock levels exist per warehouse, but transfer orders, in-transit quantities, and bin-level locations are either absent or require custom development.<\/li>\n  <li><strong>Cost accuracy:<\/strong> Items are received at <a href=\"https:\/\/aaxonix.com\/resources\/zoho-books-purchase-order-india\/\">purchase order<\/a> cost, but freight, duties, and broker fees sit in separate GL accounts rather than being allocated back to individual items. Margin reports are therefore structurally wrong.<\/li>\n  <li><strong>Pricing complexity:<\/strong> Customer-specific price lists require manual overrides, creating risk of quoting errors and making volume rebate tracking almost impossible without a spreadsheet running alongside the ERP.<\/li>\n  <li><strong>Procurement visibility:<\/strong> Blanket purchase orders, vendor performance data, and automated three-way matching are either absent or bolted on through third-party add-ons.<\/li>\n<\/ul>\n\n<p>The result is a distributor running their ERP for financial recording while managing operations through a combination of spreadsheets, a WMS that does not talk to the ERP cleanly, and a CRM that has no idea what a customer&#8217;s credit limit is. <a href=\"https:\/\/aaxonix.com\/resources\/netsuite-wholesale-distribution-india\/\">NetSuite wholesale<\/a> distribution ERP addresses each of these gaps as core, native functionality rather than add-on modules from separate vendors.<\/p>\n\n<h2>Multi-warehouse inventory management: bins, lot tracking and transfer orders in NetSuite<\/h2>\n\n<p>NetSuite&#8217;s inventory model starts at the item level and extends down to warehouse, then to zone, then to bin. For a distributor with three distribution centres, this means you can see that a particular item has 400 units total across all locations, 150 in Chicago Warehouse Bin A3, 200 in Dallas Warehouse Bin C7, and 50 currently in transit on a transfer order between them.<\/p>\n\n<h3>Bin and zone management<\/h3>\n<p>The Advanced Inventory Management module enables bin-level tracking without requiring a separate warehouse management system. Each warehouse can be configured with zones (bulk storage, pick face, quarantine) and individual bins within those zones. Receiving transactions direct putaway to specific bins, and fulfilment picks from the bin location with the highest-priority stock based on rules you define, typically FEFO (first expiry, first out) for perishables or FIFO for standard goods.<\/p>\n\n<h3>Lot and serial number tracking<\/h3>\n<p>Items that require traceability, such as food-grade chemicals, electronics with warranty requirements, or regulated components, can be tracked at the lot or serial number level. NetSuite records which lot was received on which purchase order, where it was stored, and which sales order it shipped against. This makes FDA-style traceability reports or batch recall exercises a database query rather than a warehouse paper chase.<\/p>\n\n<h3>Transfer orders and inter-company inventory<\/h3>\n<p>Moving stock between warehouses creates a transfer order that reduces available quantity at the origin location and shows in-transit on the destination. When the receiving warehouse confirms receipt, the transfer closes and stock is available to promise. For multi-subsidiary distributors, inter-company transfer orders handle the accounting entries automatically, including eliminating intercompany profit on consolidation.<\/p>\n\n<img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/warehouse-barcode-scanning.jpg\" alt=\"Warehouse worker scanning barcode inventory\" style=\"width:100%;border-radius:8px;margin:1.5rem 0\" loading=\"lazy\">\n\n<h2>Landed cost calculation: freight, duties, tariffs and how NetSuite allocates them to items<\/h2>\n\n<p>Landed cost is one of the most commonly botched areas in distribution accounting. A container arrives from an overseas supplier at a cost of $80,000. The ocean freight bill is $4,200. Customs duties are $3,600. The customs broker charges $450. If those three amounts sit in GL accounts labelled &#8220;freight expense&#8221; and &#8220;duty expense,&#8221; your item-level cost is $80,000 when the true acquisition cost was $88,250. Every margin calculation running off that inventory record is wrong by 10.3%.<\/p>\n\n<p>NetSuite&#8217;s landed cost feature allocates these ancillary charges back to the items on the original purchase order receipt. The allocation can be weighted by:<\/p>\n\n<ul>\n  <li><strong>Quantity:<\/strong> Each unit absorbs a proportional share of the total landed cost.<\/li>\n  <li><strong>Value:<\/strong> Higher-value items absorb a proportionally larger share of freight and duty.<\/li>\n  <li><strong>Weight or volume:<\/strong> Relevant for freight charges where the carrier bills by dimensional weight.<\/li>\n  <li><strong>Custom allocation:<\/strong> Manual percentages for situations where standard methods do not match the actual cost driver.<\/li>\n<\/ul>\n\n<p>The landed cost entry can be created at the time of receipt or applied retroactively once vendor invoices arrive. NetSuite posts the allocation as an inventory adjustment, updating the average cost of affected items and posting the offsetting entry to the accrued landed cost liability until the vendor bills are matched and paid.<\/p>\n\n<p>For distributors dealing with tariff complexity, particularly those sourcing across multiple countries subject to different duty schedules, NetSuite supports customs value fields at the item level and can hold harmonised tariff codes for reporting purposes, though deep customs classification still typically connects to a specialist trade compliance system via API.<\/p>\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/inline-netsuite-wholesale-distribution-2.jpg\" alt=\"netsuite wholesale distribution erp best practices\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure><h2>Purchase order management: vendor portals, blanket POs, three-way matching<\/h2>\n\n<p>Procurement in wholesale distribution is rarely transactional in the simple sense. A distributor might have a standing agreement with a manufacturer for 5,000 units of a product over a quarter, releasing specific quantities against that blanket as warehouse levels drop. They might be managing 40 active vendor relationships simultaneously, each with its own lead time, minimum order quantity, and payment term.<\/p>\n\n<h3>Blanket purchase orders<\/h3>\n<p>NetSuite supports blanket POs as a commitment against which individual releases are drawn. The blanket records the agreed total quantity and price. As releases are issued, NetSuite tracks the quantity consumed against the blanket and flags when the remaining commitment is running low. This prevents both over-purchasing against negotiated agreements and the administrative overhead of creating new POs for every individual release.<\/p>\n\n<h3>Vendor portal access<\/h3>\n<p>Through the <a href=\"https:\/\/aaxonix.com\/resources\/netsuite-suitecommerce-b2b\/\">SuiteCommerce<\/a> Advanced <a href=\"https:\/\/aaxonix.com\/resources\/zoho-books-vendor-portal-india\/\">vendor portal<\/a>, suppliers can log in to see their open purchase orders, submit advance shipping notices, and upload invoices directly. This reduces inbound email volume from vendors, gives buyers real-time visibility into what the vendor acknowledges versus what is still unconfirmed, and feeds ASN data into the receiving workflow so warehouse staff know what is arriving before the truck pulls up.<\/p>\n\n<h3>Three-way matching<\/h3>\n<p>When a vendor invoice arrives, NetSuite compares it against the original purchase order and the item receipt record. If quantities match within tolerance and prices match the PO, the bill is approved for payment automatically. If there is a discrepancy, the bill is held and routed for review. For a distributor processing 300 vendor invoices a month, this eliminates the manual cross-checking that accounts payable teams otherwise spend hours on each week.<\/p>\n\n<img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/purchase-order-supply-chain-office.jpg\" alt=\"Purchase order supply chain management\" style=\"width:100%;border-radius:8px;margin:1.5rem 0\" loading=\"lazy\">\n\n<h2>Customer-specific pricing: tiered discounts, contract pricing and volume rebates<\/h2>\n\n<p>Pricing in wholesale distribution is not list price minus a standard discount. A national hardware chain might have a contract price for every SKU in a particular product family, a volume rebate that kicks in at $500,000 in annual purchases, and special pricing for certain project bids submitted through their procurement portal. A regional contractor might have a 12% trade discount off list. A new account pays standard pricing until their volume justifies a tier review.<\/p>\n\n<p>NetSuite handles this through a layered pricing engine:<\/p>\n\n<ul>\n  <li><strong>Price levels:<\/strong> Base price, wholesale, preferred, contract. Each customer record is assigned a default price level.<\/li>\n  <li><strong>Customer-specific price overrides:<\/strong> Individual item prices can be set at the customer level, overriding the assigned price level for those specific items.<\/li>\n  <li><strong>Quantity pricing:<\/strong> Break-point discounts that automatically apply when a line item hits a threshold quantity, without requiring sales rep intervention.<\/li>\n  <li><strong>Promotions and time-limited pricing:<\/strong> Date-bound price rules that activate and expire automatically, useful for promotional periods or seasonal pricing.<\/li>\n  <li><strong>Volume rebates:<\/strong> NetSuite&#8217;s vendor rebate module (which also supports customer rebates) tracks cumulative purchases against rebate tiers and accrues the rebate liability as orders are invoiced, rather than requiring a manual true-up at period end.<\/li>\n<\/ul>\n\n<p>On the sales order, the system applies the correct price automatically based on the customer record and item combination. Sales reps see the applied price and margin, and workflow rules can require approval before a rep discounts below a floor margin threshold.<\/p>\n\n<h2>Order management and fulfilment: pick lists, pack slips, shipping integration<\/h2>\n\n<p>The fulfilment workflow in NetSuite moves from sales order through item fulfilment to shipment confirmation, with each step updating inventory, billing status, and customer-facing records.<\/p>\n\n<h3>Sales order to pick list<\/h3>\n<p>Once a sales order is approved and inventory is available to promise, NetSuite generates a pick list for the warehouse. Pick lists can be consolidated across multiple orders for wave picking, sorted by bin location to minimise travel time, and filtered by fulfilment method (will-call vs ship vs drop-ship). For distributors using a dedicated WMS, the sales order data feeds to the WMS via API and the fulfilment confirmation comes back the same way.<\/p>\n\n<h3>Pack and ship<\/h3>\n<p>The item fulfilment record captures what was actually packed: quantities, serial or lot numbers if applicable, and package dimensions and weight. This data feeds directly to the shipping carrier integration to generate a tracking number and shipping label. NetSuite&#8217;s native carrier integrations cover FedEx, UPS, and USPS. Third-party apps in SuiteApp extend this to regional carriers, LTL freight, and multi-carrier rate shopping platforms.<\/p>\n\n<h3>Drop-ship and special orders<\/h3>\n<p>For items not held in stock, NetSuite supports drop-ship orders where a purchase order is automatically created and linked to the originating sales order. When the vendor ships directly to the customer, the purchase receipt closes the sales order fulfilment without the goods ever passing through the distributor&#8217;s warehouse. Margin is captured correctly because the PO cost is linked to the specific sales order line.<\/p>\n\n<h2>NetSuite vs SAP B1 vs Dynamics 365 Business Central for wholesale distribution<\/h2>\n\n<p>Three platforms dominate the mid-market wholesale distribution ERP conversation: NetSuite, <a href=\"https:\/\/aaxonix.com\/resources\/netsuite-vs-sap-business-one-india\/\">SAP Business One<\/a>, and Microsoft Dynamics 365 Business Central. Each has a distinct profile.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Capability<\/th>\n      <th>NetSuite<\/th>\n      <th>SAP Business One<\/th>\n      <th>Dynamics 365 BC<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Deployment model<\/td>\n      <td>Cloud-native SaaS<\/td>\n      <td>On-premise or cloud (via partners)<\/td>\n      <td>Cloud or on-premise<\/td>\n    <\/tr>\n    <tr>\n      <td>Multi-subsidiary \/ <a href=\"https:\/\/aaxonix.com\/resources\/netsuite-multi-entity-india\/\">multi-entity<\/a><\/td>\n      <td>Native, OneWorld module<\/td>\n      <td>Limited; multi-entity requires SAP HANA or add-ons<\/td>\n      <td>Supported via environments, more complex<\/td>\n    <\/tr>\n    <tr>\n      <td>Landed cost<\/td>\n      <td>Native, multiple allocation methods<\/td>\n      <td>Native in SAP B1<\/td>\n      <td>Native in BC<\/td>\n    <\/tr>\n    <tr>\n      <td>Bin and warehouse management<\/td>\n      <td>Advanced WMS module native<\/td>\n      <td>Bin management available; advanced WMS via add-on<\/td>\n      <td>Bin and zone management native<\/td>\n    <\/tr>\n    <tr>\n      <td>Volume rebates<\/td>\n      <td>Native rebate module<\/td>\n      <td>Requires configuration or add-on<\/td>\n      <td>Native rebate management<\/td>\n    <\/tr>\n    <tr>\n      <td>Customisation<\/td>\n      <td><a href=\"https:\/\/aaxonix.com\/resources\/suitescript-netsuite-customisation-india\/\" class=\"sp-content-link\">SuiteScript<\/a>, SuiteFlow, SuiteBuilder<\/td>\n      <td>SDK and add-ons<\/td>\n      <td>AL language, Power Platform<\/td>\n    <\/tr>\n    <tr>\n      <td><a href=\"https:\/\/aaxonix.com\/services\/netsuite\/\" class=\"sp-content-link\">Implementation<\/a> cost (typical)<\/td>\n      <td>Higher upfront, lower ongoing IT<\/td>\n      <td>Lower licence, higher IT infrastructure<\/td>\n      <td>Mid-range; Microsoft ecosystem advantages<\/td>\n    <\/tr>\n    <tr>\n      <td>Best fit<\/td>\n      <td>Multi-location, multi-entity, cloud-first distributors<\/td>\n      <td>Single-entity distributors with SAP ecosystem<\/td>\n      <td>Microsoft-centric organisations, SMB to mid-market<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>The practical differentiator for most wholesale distributors choosing between these three platforms is the multi-entity and multi-currency question. If your business operates across more than one legal entity, or if you plan to grow into new geographies, NetSuite&#8217;s OneWorld module is the most fully developed native solution. SAP B1 and Dynamics 365 BC can accommodate multi-entity scenarios but typically require more architectural work to get there.<\/p>\n\n<p>For a single-entity distributor already running Microsoft infrastructure, Dynamics 365 BC is a strong contender on total cost of ownership. SAP B1 makes the most sense where the business has existing SAP relationships or operates in an industry where SAP-native integrations (with suppliers or logistics partners) reduce integration complexity.<\/p>\n\n<p>NetSuite wholesale distribution ERP earns its position as the leading choice for distributors that are growing, acquiring, or operating across multiple markets and need a single platform that does not require re-platforming at the next inflection point.<\/p>\n\n<div class=\"faq-section\">\n  <h2>Frequently Asked Questions<\/h2>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Is NetSuite suitable for mid-size wholesale distributors, not just enterprise?<\/p>\n    <p class=\"faq-answer\">Yes. NetSuite scales from companies doing a few million in revenue up to multi-hundred-million operations. The licensing model is modular, so a mid-size distributor can start with core financials, inventory, and order management, then add advanced modules like WMS or <a href=\"https:\/\/aaxonix.com\/resources\/netsuite-demand-planning\/\">demand planning<\/a> as they grow.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How does NetSuite handle multiple currencies in a global distribution operation?<\/p>\n    <p class=\"faq-answer\">NetSuite supports full multi-currency transactions at the purchase order, sales order, and bill level. Exchange rate tables can be updated manually or via an automatic feed. Unrealised and realised FX gains and losses are posted automatically to the general ledger.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Can NetSuite integrate with third-party shipping carriers?<\/p>\n    <p class=\"faq-answer\">Yes. NetSuite has native integrations with major carriers including FedEx, UPS, and USPS via SuiteApp connectors. It can also connect to third-party logistics platforms like ShipStation or EasyPost through SuiteCloud APIs for more complex multi-carrier scenarios.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">What is three-way matching in NetSuite and how does it work?<\/p>\n    <p class=\"faq-answer\">Three-way matching in NetSuite cross-references the original purchase order, the item receipt record, and the vendor bill before approving payment. If quantities or amounts deviate beyond a set tolerance, the bill is flagged for review, preventing overpayment and catching fulfilment discrepancies before they hit the books.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How long does a typical NetSuite implementation take for a wholesale distributor?<\/p>\n    <p class=\"faq-answer\">A standard implementation covering financials, inventory, purchasing, and order management typically takes 3 to 6 months. More complex deployments involving multi-subsidiary structures, EDI integration, or custom fulfilment workflows can run 6 to 12 months. The quality of your <a href=\"https:\/\/aaxonix.com\/resources\/data-migration-to-zoho-guide\/\">data migration<\/a> and internal project ownership are the biggest variables.<\/p>\n  <\/div>\n<\/div>\n\n<p>Wholesale distribution margins are thin enough that operational inefficiency and cost inaccuracy are not recoverable through volume alone. A properly implemented NetSuite wholesale distribution ERP gives operations directors and supply chain managers the inventory visibility, cost accuracy, and fulfilment control to run tighter operations without adding headcount. If your current ERP is forcing your team to reconcile across multiple systems to answer basic questions about margin or stock availability, that is the clearest signal that it is the wrong tool for the job.<\/p>\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>On this page Wholesale distribution looks deceptively straightforward on paper: buy goods, store them, sell them, ship them. In practice, the operational&#8230;<\/p>\n","protected":false},"author":1,"featured_media":1560,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1458","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/1458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/comments?post=1458"}],"version-history":[{"count":6,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/1458\/revisions"}],"predecessor-version":[{"id":2069,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/1458\/revisions\/2069"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media\/1560"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=1458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/categories?post=1458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/tags?post=1458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}