{"id":3176,"date":"2026-09-27T13:00:00","date_gmt":"2026-09-27T05:00:00","guid":{"rendered":"https:\/\/sourcingall.com\/?p=3176"},"modified":"2026-09-27T13:00:00","modified_gmt":"2026-09-27T05:00:00","slug":"inspection-checklist-complex-assemblies","status":"publish","type":"post","link":"https:\/\/sourcingall.com\/es\/supplier-verification\/inspection-checklist-complex-assemblies\/","title":{"rendered":"Inspection Checklist Complex Assemblies: What to Include and How to Prioritize"},"content":{"rendered":"<h1 id=\"inspection-checklist-complex-assemblies-what-to-include-and-how-to-prioritize\">Inspection Checklist Complex Assemblies: What to Include and How to Prioritize<\/h1>\n<p>A complex assembly can pass a quick cosmetic review and still fail where it matters: a connector does not mate, a safety feature is missing, a revision is wrong, or a test record belongs to another configuration. The checklist has to reveal those failures early.<\/p>\n<p>An <strong>inspection checklist complex assemblies<\/strong> is a controlled execution plan that converts product requirements into prioritized checks, defined methods, pass or fail criteria, evidence, assigned roles, sample scope, escalation, and records. It is not a generic list of boxes or a universal sampling plan.<\/p>\n<p>Put the highest-consequence, most informative checks first. A clear <strong>inspection checklist complex assemblies<\/strong> plan makes that sequence visible to the whole <a href=\"https:\/\/sourcingall.com\/es\/about-us\/\">equipo<\/a>.<\/p>\n<h2 id=\"table-of-contents\">Table of contents<\/h2>\n<ul>\n<li><a href=\"#what-is-an-inspection-checklist-complex-assemblies\">What is an inspection checklist complex assemblies?<\/a><\/li>\n<li><a href=\"#why-should-checks-be-prioritized\">Why should checks be prioritized?<\/a><\/li>\n<li><a href=\"#what-information-belongs-in-every-checklist-line\">What information belongs in every checklist line?<\/a><\/li>\n<li><a href=\"#which-inspection-layers-should-a-complex-assembly-include\">Which inspection layers should a complex assembly include?<\/a><\/li>\n<li><a href=\"#how-should-the-checklist-sequence-be-designed\">How should the checklist sequence be designed?<\/a><\/li>\n<li><a href=\"#how-should-sampling-and-records-be-controlled\">How should sampling and records be controlled?<\/a><\/li>\n<li><a href=\"#what-are-the-limits-of-an-assembly-inspection-checklist\">What are the limits of an assembly inspection checklist?<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently asked questions<\/a><\/li>\n<\/ul>\n<h2 id=\"what-is-an-inspection-checklist-complex-assemblies\">What is an inspection checklist complex assemblies?<\/h2>\n<p>An <strong>inspection checklist complex assemblies<\/strong> is a product-specific <a href=\"https:\/\/sourcingall.com\/es\/services\/\">calidad<\/a> document that directs inspectors to verify the approved configuration, critical functions, interfaces, workmanship, documentation, and release evidence in a planned order.<\/p>\n<p>ASQ defines a quality plan as one or more documents specifying the relevant standards, practices, <a href=\"https:\/\/sourcingall.com\/es\/articles\/\">recursos<\/a>, specifications, and sequence of activities. It says such plans should define responsibilities, documented instructions, suitable inspection and testing at appropriate stages, changes, and ways to measure objectives.[^1]<\/p>\n<p>For a complex assembly, the checklist should answer: what is being checked, against which requirement, by what method, at what stage, by whom, and what happens if it fails.<\/p>\n<table>\n<thead>\n<tr>\n<th>Checklist element<\/th>\n<th>What it does<\/th>\n<th>What it cannot decide alone<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Configuration reference<\/td>\n<td>Connects the inspection to the approved drawing, BOM, revision, sample, or specification<\/td>\n<td>Whether an undocumented change is acceptable<\/td>\n<\/tr>\n<tr>\n<td>Checkpoint<\/td>\n<td>Names the feature, function, interface, or record to verify<\/td>\n<td>The correct method or criterion without its linked instruction<\/td>\n<\/tr>\n<tr>\n<td>Method and tool<\/td>\n<td>States how the check is performed and which controlled equipment applies<\/td>\n<td>Whether the tool is suitable without calibration and method review<\/td>\n<\/tr>\n<tr>\n<td>Criterion<\/td>\n<td>Defines the pass, fail, measurement, or evidence requirement<\/td>\n<td>Root cause of a failed result<\/td>\n<\/tr>\n<tr>\n<td>Priority and stage<\/td>\n<td>Places high-consequence checks where they provide useful information early<\/td>\n<td>A complete product risk assessment<\/td>\n<\/tr>\n<tr>\n<td>Record and owner<\/td>\n<td>Preserves who checked what, when, and with which result<\/td>\n<td>Independent approval unless the process assigns it<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>An <strong>inspection checklist complex assemblies<\/strong> should follow the product&#8217;s actual build and test logic rather than an inspector&#8217;s memory.<\/p>\n<h2 id=\"why-should-checks-be-prioritized\">Why should checks be prioritized?<\/h2>\n<p>Prioritization is not a way to skip low-importance items. It helps an <strong>inspection checklist complex assemblies<\/strong> workflow use the right order. It is a way to sequence effort so that failures with high consequence, low detectability, high rework <a href=\"https:\/\/sourcingall.com\/es\/get-a-quote\/\">costo<\/a>, or early access needs are found before later work adds cost or hides the evidence.<\/p>\n<table>\n<thead>\n<tr>\n<th>Prioritization factor<\/th>\n<th>Question to ask<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Consequence<\/td>\n<td>If this feature fails, can it affect safety, fit, function, a required claim, customer use, or contract acceptance?<\/td>\n<\/tr>\n<tr>\n<td>Detectability<\/td>\n<td>Can the failure be found later without disassembly, specialized equipment, or destructive testing?<\/td>\n<\/tr>\n<tr>\n<td>Irreversibility<\/td>\n<td>Does the next production step close, cover, seal, program, or otherwise make the feature harder to inspect?<\/td>\n<\/tr>\n<tr>\n<td>Costo de retrabajo<\/td>\n<td>Does late discovery require dismantling, scrap, retest, or replacement of expensive material?<\/td>\n<\/tr>\n<tr>\n<td>Information gain<\/td>\n<td>Does this check quickly distinguish a broad configuration or process problem from a minor issue?<\/td>\n<\/tr>\n<tr>\n<td>External requirement<\/td>\n<td>Is this a customer, market, safety, or regulatory verification with defined timing or evidence?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>NASA&#8217;s hardware QA requirements are aerospace-specific, but they show the general logic of focusing risk-informed controls on critical hardware and process attributes and documenting verifications and pass or fail criteria before production.[^2] Use the same logic for an <strong>inspection checklist complex assemblies<\/strong> without copying NASA controls into unrelated products.<\/p>\n<h2 id=\"what-information-belongs-in-every-checklist-line\">What information belongs in every checklist line?<\/h2>\n<p>A line item needs enough context that two qualified inspectors can carry out the same check and leave an interpretable record. This is the core discipline of an <strong>inspection checklist complex assemblies<\/strong> document. A phrase like &#8220;check assembly&#8221; does not meet that standard.<\/p>\n<table>\n<thead>\n<tr>\n<th>Campo<\/th>\n<th>Example of the question it answers<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Item and configuration<\/td>\n<td>Which product, revision, subassembly, serial range, or lot is governed?<\/td>\n<\/tr>\n<tr>\n<td>Checkpoint<\/td>\n<td>Which feature, interface, document, or process evidence is being checked?<\/td>\n<\/tr>\n<tr>\n<td>Requirement source<\/td>\n<td>Which drawing, specification, work instruction, approved sample, or contract clause applies?<\/td>\n<\/tr>\n<tr>\n<td>M\u00e9todo<\/td>\n<td>Visual check, measurement, functional test, scan, torque record review, document comparison, or another controlled method?<\/td>\n<\/tr>\n<tr>\n<td>Tool or fixture<\/td>\n<td>Which approved tool, gauge, software, test fixture, or reference is needed?<\/td>\n<\/tr>\n<tr>\n<td>Acceptance criterion<\/td>\n<td>What observed result, value, limit, fit, function, or record supports pass or fail?<\/td>\n<\/tr>\n<tr>\n<td>Stage and priority<\/td>\n<td>When should the check occur, and why is it at that point?<\/td>\n<\/tr>\n<tr>\n<td>Scope and evidence<\/td>\n<td>What sample, unit, photo, data record, or result must be retained?<\/td>\n<\/tr>\n<tr>\n<td>Action on failure<\/td>\n<td>Hold, segregate, stop, recheck, escalate, investigate, or another controlled route?<\/td>\n<\/tr>\n<tr>\n<td>Owner and review<\/td>\n<td>Who performs and, where needed, independently verifies or authorizes the result?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>El <strong>inspection checklist complex assemblies<\/strong> line is the working instruction. If it cannot guide a real check, it is only a reminder.<\/p>\n<h2 id=\"which-inspection-layers-should-a-complex-assembly-include\">Which inspection layers should a complex assembly include?<\/h2>\n<p>The exact content depends on product design and risk. An <strong>inspection checklist complex assemblies<\/strong> template organizes the layers without forcing one product&#8217;s controls onto another. The layers below give a way to organize the checklist without assuming every assembly needs the same test or defect category.<\/p>\n<table>\n<thead>\n<tr>\n<th>Layer<\/th>\n<th>Typical <a href=\"https:\/\/sourcingall.com\/es\/faqs\/\">preguntas<\/a><\/th>\n<th>Boundary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Configuration and identity<\/td>\n<td>Does the product match the approved revision, BOM, label, software, and intended market configuration?<\/td>\n<td>Identity does not prove physical function<\/td>\n<\/tr>\n<tr>\n<td>Critical function and safety<\/td>\n<td>Do defined fit, protective, electrical, mechanical, sealing, performance, or other critical features meet the applicable requirement?<\/td>\n<td>A functional test may not reveal hidden workmanship or material issues<\/td>\n<\/tr>\n<tr>\n<td>Interfaces and assembly<\/td>\n<td>Do mating parts, fasteners, connectors, alignment, clearances, and moving components meet the specified condition?<\/td>\n<td>A visual fit check may not confirm all load or lifecycle performance<\/td>\n<\/tr>\n<tr>\n<td>Measurements and controlled processes<\/td>\n<td>Are critical dimensions, process records, calibrations, settings, or special-process evidence complete?<\/td>\n<td>A record may not prove the actual physical unit without traceability<\/td>\n<\/tr>\n<tr>\n<td>Workmanship and cosmetics<\/td>\n<td>Are visible surfaces, joints, markings, cleanliness, protection, and finish assessed under the approved standard?<\/td>\n<td>Cosmetic acceptance must not override functional or safety concerns<\/td>\n<\/tr>\n<tr>\n<td>Packaging and documentation<\/td>\n<td>Are required accessories, instructions, labels, certificates, reports, and packing protections present and matched?<\/td>\n<td>Complete paperwork does not correct a failed assembly<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A good <strong>inspection checklist complex assemblies<\/strong> separates these layers so a cosmetic pass cannot obscure a functional failure.<\/p>\n<h2 id=\"how-should-the-checklist-sequence-be-designed\">How should the checklist sequence be designed?<\/h2>\n<p>Map the product&#8217;s build path, then place checks where they are still informative and practical. This keeps an <strong>inspection checklist complex assemblies<\/strong> process tied to real assembly evidence. The first check is not always the easiest one. It is often the one that can avoid spending time on a product built to the wrong configuration.<\/p>\n<table>\n<thead>\n<tr>\n<th>Sequence point<\/th>\n<th>Objetivo<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Before build or receipt<\/td>\n<td>Confirm controlled documents, material identity, configuration, tools, and required first-piece or incoming evidence<\/td>\n<\/tr>\n<tr>\n<td>Before hidden or irreversible work<\/td>\n<td>Check interfaces, critical components, orientation, process settings, or values before closure, coating, sealing, programming, or final packaging<\/td>\n<\/tr>\n<tr>\n<td>During assembly<\/td>\n<td>Witness or record critical stages where the process itself creates the conformance evidence<\/td>\n<\/tr>\n<tr>\n<td>Before final cosmetics<\/td>\n<td>Run relevant high-consequence function, fit, or performance checks so cosmetic work does not delay discovery of a core failure<\/td>\n<\/tr>\n<tr>\n<td>Final assembly and pack-out<\/td>\n<td>Verify appearance, markings, accessories, pack configuration, records, and release evidence<\/td>\n<\/tr>\n<tr>\n<td>Before shipment<\/td>\n<td>Reconcile identity, disposition, traceability, exceptions, and required customer documents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&#8220;Fail fast&#8221; means performing the earliest relevant check with high consequence or high information value. It does not mean cutting the test time, ignoring a prescribed method, or using a faster but unvalidated substitute. That distinction protects the <strong>inspection checklist complex assemblies<\/strong> from becoming a speed target.<\/p>\n<h2 id=\"how-should-sampling-and-records-be-controlled\">How should sampling and records be controlled?<\/h2>\n<p>The checklist should point to the agreed inspection plan rather than inventing a sample number. This keeps the <strong>inspection checklist complex assemblies<\/strong> record aligned with the approved sampling decision. The plan must match the lot structure, product consequence, requirement type, acceptance system, and any mandatory customer or regulatory rules.<\/p>\n<table>\n<thead>\n<tr>\n<th>Record <a href=\"https:\/\/sourcingall.com\/es\/how-we-work\/\">control<\/a><\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Lot, batch, serial, and configuration identity<\/td>\n<td>Links the result to the inspected population<\/td>\n<\/tr>\n<tr>\n<td>Sample selection and basis<\/td>\n<td>Explains what the result represents and what it does not<\/td>\n<\/tr>\n<tr>\n<td>Method, tool, and revision<\/td>\n<td>Makes the result reproducible and auditable<\/td>\n<\/tr>\n<tr>\n<td>Raw result and disposition<\/td>\n<td>Preserves evidence beyond a simple pass mark<\/td>\n<\/tr>\n<tr>\n<td>Nonconformance and containment<\/td>\n<td>Connects a failure to the controlled hold, investigation, and disposition path<\/td>\n<\/tr>\n<tr>\n<td>Inspector and review identity<\/td>\n<td>Shows who performed the check and any required independent review<\/td>\n<\/tr>\n<tr>\n<td>Change history<\/td>\n<td>Prevents an obsolete checklist from controlling a changed product<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>ASQ says ANSI\/ASQ Z1.4 includes tightened, normal, and reduced attribute-sampling plans for a continuing stream of lots with specified AQL.[^3] A buyer needs the actual applicable sampling plan and standard before embedding a sampling rule in an <strong>inspection checklist complex assemblies<\/strong>.<\/p>\n<h2 id=\"what-are-the-limits-of-an-assembly-inspection-checklist\">What are the limits of an assembly inspection checklist?<\/h2>\n<p>A checklist cannot validate a weak design, make an unqualified process capable, replace <a href=\"https:\/\/sourcingall.com\/es\/\">proveedor<\/a> qualification, or discover every latent defect. Its value depends on the underlying specification, method, inspector capability, tools, access, and decision route.<\/p>\n<table>\n<thead>\n<tr>\n<th>Limit<\/th>\n<th>Practical response<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Requirement is unclear<\/td>\n<td>Stop and obtain an approved specification or technical decision before creating an appearance of control<\/td>\n<\/tr>\n<tr>\n<td>Check happens after closure<\/td>\n<td>Move the relevant verification earlier or develop a technically suitable alternate method under qualified review<\/td>\n<\/tr>\n<tr>\n<td>Tool or method is unsuitable<\/td>\n<td>Review calibration, range, resolution, method capability, and training before accepting the result<\/td>\n<\/tr>\n<tr>\n<td>Functional result fails<\/td>\n<td>Use the controlled hold, scope assessment, and investigation process rather than adjusting the checklist mark<\/td>\n<\/tr>\n<tr>\n<td>Supplier changes configuration<\/td>\n<td>Review and revise the checklist through change control before applying historic evidence<\/td>\n<\/tr>\n<tr>\n<td>Product is regulated or safety-critical<\/td>\n<td>Follow the applicable product, safety, quality, and regulatory system with qualified personnel<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The checklist should be revised when the product, process, failure history, or evidence changes. A static checklist becomes a record of old assumptions.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently asked questions<\/h2>\n<h3 id=\"what-is-an-inspection-checklist-complex-assemblies_1\">What is an inspection checklist complex assemblies?<\/h3>\n<p>An inspection checklist complex assemblies is a controlled, product-specific plan for checking configuration, functions, interfaces, workmanship, documentation, and release evidence in a defined order.<\/p>\n<h3 id=\"which-checks-should-come-first\">Which checks should come first?<\/h3>\n<p>Place checks early when a failure has high consequence, is hard to detect later, becomes hidden by a later operation, creates expensive rework, or reveals a broad configuration problem.<\/p>\n<h3 id=\"does-every-assembly-need-the-same-checklist\">Does every assembly need the same checklist?<\/h3>\n<p>No. The product design, risk, market, contract, supplier process, and applicable requirements determine the checkpoints, methods, criteria, and records.<\/p>\n<h3 id=\"what-is-a-fail-fast-check\">What is a fail-fast check?<\/h3>\n<p>A fail-fast check is an early, relevant verification with high information value or consequence. It does not authorize rushed testing or skipped steps.<\/p>\n<h3 id=\"should-cosmetic-checks-be-first\">Should cosmetic checks be first?<\/h3>\n<p>Usually not when functional, safety, fit, configuration, or hidden-process checks can fail later. Sequence should reflect risk and access, not appearance alone.<\/p>\n<h3 id=\"what-should-happen-when-a-checklist-item-fails\">What should happen when a checklist item fails?<\/h3>\n<p>Record the result, control the affected material or decision scope, and use the defined hold, escalation, investigation, and disposition process.<\/p>\n<h3 id=\"can-the-factory-change-a-checklist-during-production\">Can the factory change a checklist during production?<\/h3>\n<p>Only through controlled change review. Informal changes can break the connection between product configuration, method, evidence, and acceptance criteria.<\/p>\n<h3 id=\"how-should-the-checklist-reference-sampling\">How should the checklist reference sampling?<\/h3>\n<p>Point to the applicable approved inspection plan and identify the lot, scope, method, and record. Do not paste a generic sample number into every product checklist.<\/p>\n<h3 id=\"who-should-sign-the-checklist\">Who should sign the checklist?<\/h3>\n<p>The controlled process should identify the performer, reviewer, and any independent or release authority needed for the product and risk.<\/p>\n<h3 id=\"does-a-passing-checklist-guarantee-no-latent-defects\">Does a passing checklist guarantee no latent defects?<\/h3>\n<p>No. It shows the defined checks passed for the recorded scope. Design controls, process controls, supplier quality, testing, and traceability still matter.<\/p>\n<h2 id=\"what-is-the-practical-rule\">What is the practical rule?<\/h2>\n<p>Put the checks that can prevent the worst escape before the work that makes them hard to see. That is the practical rule for an <strong>inspection checklist complex assemblies<\/strong>.<\/p>\n<h2 id=\"references\">Referencias<\/h2>\n<p>[^1]: <a href=\"https:\/\/asq.org\/quality-resources\/quality-plans\" target=\"_blank\" rel=\"noopener\">ASQ, &#8220;What is a Quality Plan?&#8221;<\/a><\/p>\n<p>[^2]: <a href=\"https:\/\/nodis3.gsfc.nasa.gov\/displayDir.cfm?Internal_ID=N_PR_8735_002C_&amp;page_name=Chapter4\" target=\"_blank\" rel=\"noopener\">NASA, &#8220;NPR 8735.2C, Chapter 4: Program and Project Quality Management for Mission Hardware Production,&#8221; effective March 12, 2021<\/a><\/p>\n<p>[^3]: <a href=\"https:\/\/asq.org\/quality-resources\/z14-z19\" target=\"_blank\" rel=\"noopener\">ASQ, &#8220;ASQ\/ANSI Quality Standards Z1.4 &amp; Z1.9&#8221;<\/a><\/p>\n<h2 id=\"related-reading\">Related reading<\/h2>\n<ul>\n<li><a href=\"https:\/\/sourcingall.com\/es\/incoming-inspection-plan-buyers\/\">Incoming inspection plan for buyers<\/a><\/li>\n<li><a href=\"https:\/\/sourcingall.com\/es\/factory-calibration-audit\/\">Factory calibration audit<\/a><\/li>\n<li><a href=\"https:\/\/sourcingall.com\/es\/cosmetic-defect-acceptance-criteria\/\">Cosmetic defect acceptance criteria<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Build an inspection checklist complex assemblies can use to prioritize critical function, fit, evidence, cosmetics, and release checks.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_internal_links_processed":["1"],"_uag_page_assets":["a:9:{s:3:\"css\";s:263:\".uag-blocks-common-selector{z-index:var(--z-index-desktop) !important}@media (max-width: 976px){.uag-blocks-common-selector{z-index:var(--z-index-tablet) !important}}@media (max-width: 767px){.uag-blocks-common-selector{z-index:var(--z-index-mobile) !important}}\n\";s:2:\"js\";s:0:\"\";s:18:\"current_block_list\";a:15:{i:0;s:11:\"core\/search\";i:1;s:10:\"core\/group\";i:2;s:12:\"core\/heading\";i:3;s:17:\"core\/latest-posts\";i:4;s:20:\"core\/latest-comments\";i:5;s:13:\"core\/archives\";i:6;s:15:\"core\/categories\";i:8;s:25:\"greenshift-blocks\/heading\";i:9;s:22:\"greenshift-blocks\/text\";i:10;s:14:\"core\/paragraph\";i:12;s:18:\"core\/legacy-widget\";i:13;s:17:\"core\/social-links\";i:15;s:16:\"core\/social-link\";i:16;s:21:\"trp\/language-switcher\";i:17;s:9:\"core\/html\";}s:8:\"uag_flag\";b:0;s:11:\"uag_version\";s:10:\"1791075603\";s:6:\"gfonts\";a:0:{}s:10:\"gfonts_url\";s:0:\"\";s:12:\"gfonts_files\";a:0:{}s:14:\"uag_faq_layout\";b:0;}"]},"categories":[33],"tags":[],"class_list":["post-3176","post","type-post","status-publish","format-standard","hentry","category-supplier-verification"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false},"uagb_author_info":{"display_name":"admin","author_link":"https:\/\/sourcingall.com\/es\/author\/admin\/"},"uagb_comment_info":0,"uagb_excerpt":"Build an inspection checklist complex assemblies can use to prioritize critical function, fit, evidence, cosmetics, and release checks.","_links":{"self":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/3176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/comments?post=3176"}],"version-history":[{"count":1,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/3176\/revisions"}],"predecessor-version":[{"id":3387,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/posts\/3176\/revisions\/3387"}],"wp:attachment":[{"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/media?parent=3176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/categories?post=3176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sourcingall.com\/es\/wp-json\/wp\/v2\/tags?post=3176"}],"curies":[{"name":"gracias","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}