Apixaban API in Generic Tablets: Why Dissolution Starts With the API
by Healthwire
SHARES
Dissolution is not a final box to tick after an apixaban tablet has already been formulated. It reflects decisions made much earlier about the API, formulation, analytical method, and manufacturing process.
FDA’s February 2026 draft product-specific guidance for apixaban recommends that generic developers provide a dissolution-method development report and demonstrate that the method can detect changes in critical quality attributes that could affect drug-product performance.
That recommendation highlights an important development reality: a dissolution profile is shaped by the API, formulation, and process together.
Apixaban tablets are marketed at low strengths, including 2.5 mg and 5 mg. When only a small quantity of drug substance is distributed through a tablet and then has to move reproducibly into solution, material differences can become visible in dissolution performance even when routine incoming tests remain within specification.
For formulation, analytical, regulatory, and sourcing teams, the useful question is therefore not:
“What particle size should every Apixaban API have?”
There is no universal value suitable for every formulation.
A better question is:
“Which API attributes did our development work show to affect product performance, and can commercial supply control them consistently?”
Why Does Particle Size Enter Apixaban Development So Early?
Particle size affects the surface area available for dissolution. When dissolution is sensitive to API particle size, a commercial description such as “micronized” is no longer enough to define the material.
A 2025 physiologically based biopharmaceutics modeling study evaluated particle size, granulation method, and dissolution conditions as variables in apixaban tablet development. Changes in particle size materially influenced modeled dissolution behavior. Within the formulation studied, particle sizes up to approximately 20–25 μm were associated with very rapid dissolution.
That finding is useful development evidence.
It is not a universal purchasing specification for every apixaban product.
The difference matters. Published research can identify a material attribute that deserves investigation, but the final control strategy needs to come from the actual formulation, process, analytical method, and development data used for the product being developed.
Copying a particle-size value from a paper into an API purchase specification can create the appearance of technical control without proving that the limit is relevant to the finished tablet.
Why Is “Micronized” Not a Particle-Size Specification?
Commercial API discussions often reduce particle-size information to a single word:
micronized.
That tells a formulation team very little.
A usable particle-size requirement needs a defined test method, sample-preparation procedure, dispersion conditions where relevant, and distribution criteria that both the pharmaceutical manufacturer and API supplier understand.
D10, D50, and D90 values may provide a more useful picture of particle-size distribution than simply describing a powder as “fine” or “micronized.”
The analytical method also matters.
Different dispersion procedures or measurement techniques can produce apparently different values even when the underlying material has not changed in a way that matters to the formulation. For that reason, a particle-size limit should travel with the method used to generate it.
The goal is not to put more numbers on a CoA.
It is to establish a repeatable material control that has a demonstrated relationship with product performance.
How Do You Know Whether a Dissolution Shift Comes From the API?
When a dissolution profile changes after a new API lot arrives, the incoming material becomes an obvious suspect.
Sometimes that is the right explanation. Often it is only part of the picture.
Granulation, excipient properties, compression force, tablet structure, disintegration behavior, moisture, and other processing variables can also influence dissolution.
A useful investigation therefore compares API and drug-product variables together.
|
Change observed |
API question |
Formulation or process question |
|
Dissolution slows with a new API lot |
Did PSD or another relevant material attribute move? |
Were granulation and compression conditions unchanged? |
|
Early dissolution becomes more variable |
Is the API distribution broader or sampling less representative? |
Has blend, granule, or tablet uniformity changed? |
|
Development and scale-up batches differ |
Does commercial API match the development grade? |
Did scale-up alter wetting, granulation, or tablet structure? |
|
Different tablet strengths behave differently |
Are relevant API controls consistent across batches? |
Are the formulations proportionally similar and dissolution conditions suitable? |
FDA’s February 2026 draft guidance recommends comparative in vitro dissolution when supporting waiver requests for additional strengths, together with an acceptable bioequivalence study on the 5 mg strength and proportional similarity of the formulations.
The guidance also recommends a dissolution method capable of detecting relevant changes in critical quality attributes that may affect drug-product performance.
That makes discriminating dissolution useful for more than routine release testing.
A method that can reveal meaningful material or process differences is much more valuable during development than one that simply produces a passing result across every experimental condition.
What API Attributes Should Be Locked Before Scale-Up?
A development team does not need to freeze every measurable property of Apixaban API.
It does need to identify and control the properties that have shown a meaningful relationship with product performance.
Particle-size distribution may become one of those attributes if dissolution and formulation work demonstrate sufficient sensitivity.
If it does, the control strategy should include more than a target number. It may need:
- the particle-size analytical method;
- relevant sample-preparation or dispersion conditions;
- development-lot data;
- an acceptable distribution range;
- commercial-lot expectations;
- confirmation of the grade intended for routine production.
Representative material near the edge of an established range can also be useful when challenging the dissolution method.
If development has already shown that changes in an API attribute can alter product performance, the dissolution method should ideally be able to detect a meaningful shift.
That approach is stronger than choosing an unusually narrow particle-size range simply because it appears more rigorous.
Why Does the Development Sample Need a Commercial Identity?
“Sample approved” sounds reassuring, but it can hide an important gap.
A laboratory sample may have the expected assay and appearance while still differing from later commercial material in particle-size distribution, manufacturing scale, processing history, or another attribute relevant to tablet performance.
If the development team cannot identify which routine commercial grade the approved sample represents, a material change may effectively occur after formulation work is already complete.
The handoff from R&D to procurement should therefore identify the material, not merely the supplier.
Depending on what development has shown to matter, that record may include:
- API grade;
- manufacturing source;
- relevant particle-size method and distribution;
- representative batch information;
- solid-state information where justified;
- other API attributes linked to dissolution or processing behavior.
This is not intended to become another broad supplier-audit checklist.
Its purpose is narrower: preserve continuity between the API used to establish product performance and the material later purchased for commercial manufacturing.
How Does This Affect Generic Apixaban Tablet Development?
FDA’s February 2026 draft product-specific guidance recommends a fasting, single-dose in vivo bioequivalence study using the 5 mg strength, with apixaban measured in plasma.
For additional strengths, the guidance also discusses proportional similarity and comparative dissolution.
These recommendations make early understanding of API-related dissolution variables particularly useful. If material variability is discovered only after scale-up, formulation teams may begin adjusting granulation, compression, or other process parameters to compensate for a problem that actually began with uncontrolled API characteristics.
That can make the development history harder to interpret.
A better approach is to connect selected API controls with product-development evidence.
If particle size is controlled, the development team should be able to explain why it matters. If another physical or solid-state property becomes relevant, the same principle applies.
A material limit supported by dissolution or process data is more defensible than one copied from a supplier’s standard specification.
The best API specification is therefore not necessarily the longest.
It is the one that preserves the material knowledge generated during development.
What Should Procurement Receive From the Development Team?
Procurement should not have to reconstruct formulation requirements from laboratory notebooks after supplier discussions have already started.
Before commercial sourcing begins, R&D can translate the relevant development findings into a concise material brief.
That brief may state:
- the exact API grade required;
- he material attributes linked to successful dissolution performance;
- the analytical methods used to measure them;
- the sample quantity needed for evaluation;
- expectations for representative commercial-lot material;
information that should trigger notification if the commercial material changes.
This creates a cleaner handoff between formulation and sourcing.
Instead of asking suppliers whether they can provide “Apixaban API,” procurement can ask whether the offered commercial grade matches the material characteristics already demonstrated to work.
That distinction can prevent a technically acceptable quotation from turning into a formulation investigation later.
Where Can Development and Sourcing Teams Start Product Discovery?
Once the material brief is defined, API discovery becomes much more focused.
Development and sourcing teams can explore APIs for cardiovascular system drugs on PharmaSources when identifying candidate materials for further technical evaluation.
The category should be treated as a product-discovery starting point rather than evidence that any listed API will reproduce the dissolution profile established during development.
PharmaSources covers APIs alongside pharmaceutical intermediates, excipients, finished dosage forms, laboratory products, packaging, and other pharmaceutical supply categories. This allows sourcing teams to move from a defined technical requirement to relevant product and supplier discovery without changing the development criteria simply to fit what is commercially available.
The next conversation should focus on whether the proposed commercial material can support the particle-size, batch, analytical, and change-notification information already established by the project.
When the technical brief is sufficiently defined and several candidate sources need to be approached, buyers can submit an Apixaban API sourcing request using the same formulation-critical requirements for each candidate.
This keeps the RFQ focused on material fit rather than simply availability and price.
Product and supplier discovery can then sit with the sourcing platform while formulation, analytical, QA, and regulatory teams retain control of the technical decision.
Conclusion
For generic apixaban tablets, dissolution performance does not begin at the dissolution bath.
It begins with decisions made much earlier about the API, analytical method, formulation, and manufacturing process.
Particle size illustrates the point well. Development research shows that it can influence apixaban dissolution, while FDA’s current draft product-specific guidance recommends dissolution-method development capable of detecting changes in critical quality attributes that may affect drug-product performance.
The appropriate response is not to impose an arbitrary particle-size number on every supplier.
Use development evidence to identify the material range that works. Keep the analytical method consistent. Confirm that commercial material represents the evaluated grade. Then carry those requirements into sourcing before quotation and supply pressure begin driving the decision.
That turns an API specification from a purchasing document into a practical bridge between formulation development and reproducible commercial production.
FAQ
Does every Apixaban API need the same particle-size specification?
No. Particle size can influence dissolution, but the appropriate control should be justified by the specific formulation, process, analytical method, and development data. A value reported in a published study or another supplier’s specification should not automatically become the purchasing limit.
Why is dissolution important in generic apixaban development?
FDA’s February 2026 draft product-specific guidance recommends dissolution testing as part of drug-product quality control and discusses comparative dissolution when supporting waiver requests for additional strengths. It also recommends demonstrating that the dissolution method can detect relevant changes in critical quality attributes.
What should procurement carry over from the development stage?
Procurement should receive the API attributes that development has linked to product performance together with the analytical methods used to evaluate them. For apixaban, this may include relevant particle-size information, representative batch data, the commercial grade evaluated during development, and notification expectations for changes that could affect those attributes.
