Lex et Mercatura by BantayBid · PhilGEPS Update
PhilGEPS 1.5 Is Being Phased Out: What Suppliers Need to Check in 2026
PhilGEPS 1.5 is not disappearing on one nationwide date. The transition is staggered by procuring entity, which means suppliers should identify the agency first and then verify which PhilGEPS platform governs its new postings.
Published: September 6, 2026 · Updated: September 6, 2026
The practical issue: there is no single cutoff for every agency
PS - DBM has been decommissioning PhilGEPS 1.5 in stages. The relevant deadline depends on the procuring entity covered by the applicable advisory. For suppliers, the safest starting point is therefore not the platform itself but the identity of the government office issuing the procurement.
This distinction matters because two agencies may be at different points in the transition. A supplier should not assume that an opportunity is absent merely because it does not appear in the first PhilGEPS platform searched.
Executive Branch: new PhilGEPS 1.5 postings ended on July 31
Under PS Advisory 2026-19, departments under the Executive Branch - including their regional and provincial offices, district offices and attached agencies, together with the Office of the President and the Office of the Vice President - could post new procurement opportunities in PhilGEPS 1.5 only until July 31, 2026.
Beginning August 1, 2026, the advisory states that no new procurement opportunities from those covered entities are to be published in PhilGEPS 1.5. For applicable procurement activities, those entities must transition to the eBidding Facility of the Modernized PhilGEPS.
Other remaining agencies: the October 31 date applies only to the covered group
PS Advisory 2026-18 clarified the scope of the "all remaining government agencies" category under the revised Batch 3 timetable. Procuring entities falling within that category may post new procurement opportunities in PhilGEPS 1.5 only until October 31, 2026.
Starting November 1, 2026, no new procurement opportunities are to be published in PhilGEPS 1.5 by the entities covered by that category. The October 31 date should therefore not be treated as a universal deadline for every government office.
Older procurements can still appear after a cutoff
A cutoff on new postings does not mean every activity in PhilGEPS 1.5 stops on that date. PS - DBM states that a procuring entity may still finalize ongoing procurements and post awards and contracts for opportunities that were posted on or before its applicable cutoff date.
That is why an older PhilGEPS 1.5 record may continue to receive later procurement updates even after the agency has stopped publishing new opportunities there.
What suppliers should do now
- Identify the procuring entity first. The applicable transition rule depends on the government office involved.
- Check the latest PS - DBM advisory for that entity. Do not rely on a remembered migration date or an old checklist.
- Monitor the Modernized PhilGEPS for new opportunities where the entity has already transitioned.
- Continue checking PhilGEPS 1.5 where the entity remains within an authorized posting window.
- Keep watching older PhilGEPS 1.5 procurements for awards and contract postings. Those records may continue after the cutoff for new postings.
- Verify the actual bid deadline and procurement documents at the official source before acting.
Why this matters commercially
The transition is not merely a technical change in government software. It affects where suppliers look for business. A company that searches only one platform without first checking the procuring entity's migration status risks overlooking a current notice or misreading an older procurement record.
The practical discipline is simple: identify the agency, verify its current transition rule, search the correct platform for new opportunities, and continue monitoring older records where the procurement remains active.
Official sources
PhilGEPS migration dates have changed through later advisories. Lex et Mercatura will treat the most recent applicable PS - DBM guidance as controlling for future updates and will not assume that one migration date applies to every procuring entity.